pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,572,239
10 transactions · 9 stateful · 2026-05-05 10:14:14 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,572,239 · 10 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
1w03w14w05w16w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xad5f0940…e334
0x065c9d…c394
5 touches
3 conflicts
0x203e9530…ab5a
0x065c9d…c394
5 touches
3 conflicts
0x7eeb9792…3604
0xc8689a…ee79
4 touches
1 conflict
0x86755415…f7d2
0x065c9d…c394
4 touches
1 conflict
0x50997ada…364d
0x8d0464…4402
4 touches
1 conflict
0xc5564f8e…f4bf
0x8d0464…4402
4 touches
1 conflict
0xf0f673fd…37a7
0x8d0464…4402
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: 0x065c9d28…a9c394
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity