pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,667,999
← previous block
next block →
recent activity
Analyzing
Block #74,667,999
11 transactions · 9 stateful · 2026-05-15 03:10:55 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,667,999
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
updatePrices
#4
0x5bf9264c
#5
0x5bf9264c
#6
swapExactIn
· blocks 1
#8
0x6a068f36
#9
setData
#10
exactInputSingle
#7
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x465a0b…3980
4 touches
1 conflict
0x00000000…0005
0x465a0b…3980
4 touches
1 conflict
0x3b56d5f7…d11b
0x465a0b…3980
4 touches
1 conflict
0xe069120c…952c
0x000000…012a
4 touches
1 conflict
0xb0f4dbcb…926a
0x754704…b603
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x93afca4c…b478
0x1b6862…e19c
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer:
0x465a0b35…b53980
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity