pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,065,410
10 transactions · 9 stateful · 2026-04-28 10:48:16 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,065,410 · 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
4w05w06w17w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x131a2e…0da9
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x9187e5b8…51b9
0x065c9d…c394
2 touches
0 conflicts
0xac9fc41c…e8bc
0x065c9d…c394
2 touches
0 conflicts
0xf2d1255e…e414
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x131a2e…0da9
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