pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,172,249
← previous block
next block →
recent activity
Analyzing
Block #72,172,249
9 transactions · 7 stateful · 2026-05-03 13:42:45 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,172,249
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x15ea9545
#2
0x98717539
· blocks 1
#4
withdraw
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
forward
#8
setData
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a7
0x8d66a4…3095
4 touches
1 conflict
0xb7cbb23c…9a52
0x1efe02…37d6
2 touches
0 conflicts
0x1728ed63…499c
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0x8f38186f…4fa8
0xea1b8e…c5ec
2 touches
0 conflicts
0x9c8d6dd6…d619
0xea1b8e…c5ec
2 touches
0 conflicts
0x9c8d6dd6…d61a
0xea1b8e…c5ec
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:
0x8d66a43f…113095
1 conflict on slot
0x96504a6391…e952d2
Audit this contract →
← previous block
·
next block →
recent activity