pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,283,240
7 transactions · 5 stateful · 2026-05-04 02:08:35 UTC
Parallelism
57/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,283,240 · 7 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0a7ca33…3c7e
0x34b655…2a6f
6 touches
3 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
6 touches
3 conflicts
0xcbad3868…f129
0x34b655…2a6f
4 touches
1 conflict
0x257251ca…49b8
0x34b655…2a6f
4 touches
1 conflict
0x23951077…539b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x77905798…fe3d
0x34b655…2a6f
4 touches
1 conflict
0x908d4442…2c4b
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: 0x34b6552d…112a6f
3 conflicts on slot 0xf0a7ca3337…9d3c7e
Audit this contract →
← previous block·next block →recent activity