pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,296,325
← previous block
next block →
recent activity
Analyzing
Block #72,296,325
8 transactions · 8 stateful · 2026-05-04 03:36:29 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,296,325
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#2
0x8400324b
#4
0xbf388c71
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#3
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22473194…66f7
0x065c9d…c394
4 touches
1 conflict
0x136d0239…2332
0x065c9d…c394
3 touches
1 conflict
0xcd31b849…0777
0x065c9d…c394
3 touches
1 conflict
0xbf04f37d…85f2
0x2a68ba…90c5
2 touches
0 conflicts
0x2e2214a9…fe0d
0x8d0464…4402
2 touches
0 conflicts
0x554f1ada…6916
0x8d0464…4402
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:
0x065c9d28…a9c394
1 conflict on slot
0x24968e6db4…f00132
Audit this contract →
← previous block
·
next block →
recent activity