pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,324,396
7 transactions · 6 stateful · 2026-05-08 21:42:58 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,324,396 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x64461c10…e86d
0x34b655…2a6f
4 touches
1 conflict
0x819ea6d6…cd6f
0x34b655…2a6f
4 touches
1 conflict
0xb389d45f…8a4c
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0xeedfbc…f7dc
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0xdbadf6b0…43b2
0xeedfbc…f7dc
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: 0x34b6552d…112a6f
1 conflict on slot 0xb91a6f59b9…c8722c
Audit this contract →
← previous block·next block →recent activity