pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,366,007
← previous block
next block →
recent activity
Analyzing
Block #72,366,007
9 transactions · 8 stateful · 2026-05-04 11:20:38 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,366,007
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x3f5c179b
#2
updateDataFeedsValuesPartial
#3
0xed82b078
#4
0x69f8817e
#5
setData
#6
0x39435dac
· blocks 2
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0xd6aabe89…92f5
0x34b655…2a6f
4 touches
1 conflict
0x05bc9737…65e0
0x065c9d…c394
2 touches
0 conflicts
0x20507bb1…8411
0x065c9d…c394
2 touches
0 conflicts
0x32881b99…5494
0x065c9d…c394
2 touches
0 conflicts
0x83f619c3…2571
0x065c9d…c394
2 touches
0 conflicts
0x9c0a2d7c…6fdd
0x065c9d…c394
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:
0x34b6552d…112a6f
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity