pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,937,712
← previous block
next block →
recent activity
Analyzing
Block #75,937,712
10 transactions · 9 stateful · 2026-05-21 00:35:03 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,937,712
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
reallocate
#2
0xab083028
· blocks 1
#3
0x0f6795d9
#4
forward
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
#8
0xe9316489
#9
setData
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x99603e38…6dc5
0x065c9d…c394
3 touches
1 conflict
0x93365598…ba32
0x065c9d…c394
3 touches
1 conflict
0x0dfebe1d…6083
0x09475a…400f
2 touches
0 conflicts
0x1151b256…b43b
0x09475a…400f
2 touches
0 conflicts
0x88c7bc1a…32a8
0x09475a…400f
2 touches
0 conflicts
0xb05b4688…bc26
0x09475a…400f
2 touches
0 conflicts
0xb25823d5…e4d9
0x754704…b603
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-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity