pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,746,213
12 transactions · 9 stateful · 2026-05-01 14:26:10 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,746,213 · 12 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x956c9951…4596
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfe6a8c90…bb2e
0x065c9d…c394
4 touches
1 conflict
0x0698d0a4…00b9
0x065c9d…c394
3 touches
1 conflict
0xa7263aad…06f7
0x065c9d…c394
3 touches
1 conflict
0x742c69dd…63d0
0x065c9d…c394
3 touches
1 conflict
0x83cbc19e…bc79
0x065c9d…c394
3 touches
1 conflict
0xd74d5bed…5e7e
0x2a68ba…90c5
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 0x956c99517a…d94596
Audit this contract →
← previous block·next block →recent activity