pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,296,370
10 transactions · 10 stateful · 2026-05-04 03:36:46 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,296,370 · 10 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
1w02w13w04w25w06w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x74e71984…ae90
0x2a68ba…90c5
6 touches
3 conflicts
0x86499a4b…1436
0x065c9d…c394
6 touches
3 conflicts
0xfc8818ce…fb91
0x065c9d…c394
5 touches
3 conflicts
0xdf08a43d…ec26
0x065c9d…c394
5 touches
3 conflicts
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0x40720420…0ce2
0xd32edf…ff58
3 touches
1 conflict
0x2cf63f97…725f
0x065c9d…c394
3 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