pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,892,552
11 transactions · 10 stateful · 2026-04-27 15:37:18 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,892,552 · 11 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
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4a8dcbfc…8cfc
0x065c9d…c394
4 touches
1 conflict
0x66bf8457…9c07
0x065c9d…c394
4 touches
1 conflict
0xb0ce029d…4859
0x065c9d…c394
4 touches
1 conflict
0xcf1a0899…14e9
0x065c9d…c394
4 touches
1 conflict
0xa3dc6f35…13e9
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x8956cb26…42fa
0x73ada1…8be0
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