pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,496,799
← previous block
next block →
recent activity
Analyzing
Block #72,496,799
11 transactions · 8 stateful · 2026-05-05 01:51:56 UTC
Parallelism
73
/100
Blocked
25
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,496,799
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
0x5bf9264c
#5
0x5bf9264c
#6
0x98717539
· blocks 2
#9
0x3f5c179b
#10
setData
#7
0x98717539
· blocks 1
#8
0x98717539
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
0x8a35acfb…d1ae
0x8d66a4…3095
6 touches
3 conflicts
0x462c8be7…4f83
0x8d66a4…3095
4 touches
1 conflict
0x5ba51e87…44ee
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ad
0x8d66a4…3095
4 touches
1 conflict
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
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
3 conflicts on slot
0x8a35acfbc1…6bd1ae
Audit this contract →
← previous block
·
next block →
recent activity