pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,237,374
← previous block
next block →
recent activity
Analyzing
Block #77,237,374
11 transactions · 11 stateful · 2026-05-27 00:52:23 UTC
Parallelism
64
/100
Blocked
27
%
Avg conflicts / tx
0.64
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,237,374
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
batchUpdate
· blocks 1
#2
batchUpdate
· blocks 3
#5
0xab083028
#6
updateDataFeedsValuesPartial
#8
forward
#9
setData
#10
execOrders
#3
0xed82b078
· blocks 2
#4
0xab083028
· blocks 1
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8aab7db…a319
0xa6afd3…d132
8 touches
6 conflicts
0xdf8c628d…34f2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x775ca9d3…4d3c
0xa6afd3…d132
3 touches
1 conflict
0xf2e52e15…7ace
0xa6afd3…d132
3 touches
1 conflict
0x49164b08…b4ea
0x065c9d…c394
2 touches
0 conflicts
0x758121ff…ccfe
0x065c9d…c394
2 touches
0 conflicts
0x10abefc9…c9bc
0x1d1325…2305
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:
Kuru Exchange: Market-WETH/USDC
6 conflicts on slot
0xe8aab7db02…86a319
Audit this contract →
← previous block
·
next block →
recent activity