pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,098,494
12 transactions · 10 stateful · 2026-05-03 05:31:25 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,098,494 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcfdf8a1c…6e1e
0x065c9d…c394
3 touches
1 conflict
0xdd6545f4…8862
0x065c9d…c394
3 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x26bbcb47…263f
0x34b655…2a6f
2 touches
0 conflicts
0x58d58de6…f40a
0x34b655…2a6f
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
3 conflicts on slot 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity