pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,399,601
9 transactions · 6 stateful · 2026-05-04 15:04:33 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,399,601 · 9 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7707da20…51b4
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x35c00106…0382
0x065c9d…c394
2 touches
0 conflicts
0x7bdc89f2…eaec
0x065c9d…c394
2 touches
0 conflicts
0xbb8a814f…af11
0x065c9d…c394
2 touches
0 conflicts
0xd2b6132f…07fe
0x065c9d…c394
2 touches
0 conflicts
0xe1c478a0…858d
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity