pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,557,878
14 transactions · 13 stateful · 2026-04-30 17:32:23 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,557,878 · 14 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
1w02w03w14w25w36w48w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x414cc9…c1ba
10 touches
10 conflicts
0x00000000…000a
0x414cc9…c1ba
10 touches
10 conflicts
0x00000000…000c
0x414cc9…c1ba
10 touches
10 conflicts
0x00000000…000e
0x414cc9…c1ba
10 touches
10 conflicts
0x00000000…0002
0x414cc9…c1ba
10 touches
10 conflicts
0xf6522223…0d40
0x414cc9…c1ba
5 touches
3 conflicts
0x8a35acfb…d1a5
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a6
0x8d66a4…3095
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: 0x414cc990…78c1ba
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity