pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,370,815
5 transactions · 4 stateful · 2026-05-04 11:52:39 UTC
Parallelism
60/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,370,815 · 5 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5058e980…fd81
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe190d507…f5ce
0x065c9d…c394
3 touches
1 conflict
0x0a7a3fd1…c7a2
0x065c9d…c394
2 touches
0 conflicts
0x59a992b4…3a62
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x8758a729…847c
0x065c9d…c394
2 touches
0 conflicts
0xc4cb5fb2…6a56
0x065c9d…c394
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
1 conflict on slot 0x5058e980f5…91fd81
Audit this contract →
← previous block·next block →recent activity