pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,877,673
15 transactions · 12 stateful · 2026-04-27 13:58:17 UTC
Parallelism
87/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,877,673 · 15 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
1w02w16w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15538d55…6731
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0xb587cf5f…719a
0x065c9d…c394
3 touches
1 conflict
0x4d062ee9…398e
0x065c9d…c394
3 touches
1 conflict
0xdbdae4a5…0aa1
0x065c9d…c394
3 touches
1 conflict
0x0395cae7…4e17
0xd32edf…ff58
3 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
1 conflict on slot 0x15538d552c…dc6731
Audit this contract →
← previous block·next block →recent activity