pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,065,662
10 transactions · 9 stateful · 2026-04-28 10:49:57 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,065,662 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x322648e8…ee57
0x065c9d…c394
4 touches
1 conflict
0x44b87fcb…1ddf
0x065c9d…c394
4 touches
1 conflict
0x6090faa0…cc1f
0x065c9d…c394
4 touches
1 conflict
0x8cef270f…fed6
0x065c9d…c394
4 touches
1 conflict
0x95b86448…0d01
0x065c9d…c394
4 touches
1 conflict
0x1cdb5820…6504
0x065c9d…c394
2 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: 0x065c9d28…a9c394
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity