pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,201,221
← previous block
next block →
recent activity
Analyzing
Block #73,201,221
9 transactions · 7 stateful · 2026-05-08 08:03:30 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,201,221
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
· blocks 1
#3
execute
#5
0x0f6795d9
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
setData
#2
0x98717539
· blocks 1
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d1bb389…c7d9
0x8d66a4…3095
4 touches
1 conflict
0x143dba04…1b98
0x8d66a4…3095
4 touches
1 conflict
0x17cd1479…00bb
0x8d66a4…3095
4 touches
1 conflict
0x1e451306…7993
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a5
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a6
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1aa
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ab
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
1 conflict on slot
0x9d1bb3891b…cac7d9
Audit this contract →
← previous block
·
next block →
recent activity