pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,366,014
7 transactions · 6 stateful · 2026-05-04 11:20:41 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,366,014 · 7 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
1w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x05bc9737…65e0
0x065c9d…c394
2 touches
0 conflicts
0x08a01a04…a406
0x065c9d…c394
2 touches
0 conflicts
0x18b0909f…815c
0x065c9d…c394
2 touches
0 conflicts
0x283a9549…68d7
0x065c9d…c394
2 touches
0 conflicts
0x76cdcdd0…3f23
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: 0x2a68ba18…8e90c5
1 conflict on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity