pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,333,872
14 transactions · 9 stateful · 2026-05-08 22:45:58 UTC
Parallelism
79/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,333,872 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x02952e27…66f1
0x6657d1…8ccc
2 touches
0 conflicts
0x0653dcc3…f4a9
0x6657d1…8ccc
2 touches
0 conflicts
0x165ba7b8…14a3
0x6657d1…8ccc
2 touches
0 conflicts
0x1e6cd1a3…a039
0x6657d1…8ccc
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity