pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,741,965
10 transactions · 10 stateful · 2026-05-01 13:57:50 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,741,965 · 10 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x504bf28b…6b76
0x065c9d…c394
4 touches
1 conflict
0xef698ab3…600c
0x065c9d…c394
3 touches
1 conflict
0x31770fe4…4e03
0x065c9d…c394
3 touches
1 conflict
0x66c6ef69…a342
0x065c9d…c394
3 touches
1 conflict
0x5b01321a…8163
0x065c9d…c394
2 touches
0 conflicts
0xa22d4a11…7c5e
0x065c9d…c394
2 touches
0 conflicts
0x508387de…c644
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity