pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,394,859
16 transactions · 12 stateful · 2026-05-04 14:32:56 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,394,859 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w29w310w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaac809a8…a370
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x6364bde1…1038
0x065c9d…c394
4 touches
1 conflict
0x741bb61f…83ed
0x065c9d…c394
3 touches
1 conflict
0x46cb45de…a568
0x188d58…ea8e
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x614b85…a284
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: 0xd32edf66…9fff58
10 conflicts on slot 0xaac809a823…01a370
Audit this contract →
← previous block·next block →recent activity