pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,575,658
32 transactions · 24 stateful · 2026-05-05 10:37:01 UTC
Parallelism
84/100
Blocked
54%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,575,658 · 32 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
2w04w05w17w18w010w114w015w118w019w120w221w323w224w225w326w327w431w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
10 touches
10 conflicts
0xbbee74c2…567a
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x34ced8e0…f6d6
0xd32edf…ff58
7 touches
6 conflicts
0xbad68552…e6bf
0x34b655…2a6f
6 touches
3 conflicts
0xeaf4270f…92b0
0x065c9d…c394
5 touches
3 conflicts
0x74e71984…ae90
0x2a68ba…90c5
4 touches
1 conflict
0xbf04f37d…85f2
0x2a68ba…90c5
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
10 conflicts on slot 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity