pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,995,684
11 transactions · 10 stateful · 2026-04-28 03:04:11 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,995,684 · 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
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8b05c3b…077c
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x779eaa24…2a9c
0x065c9d…c394
4 touches
1 conflict
0x0e0b4515…578c
0x065c9d…c394
3 touches
1 conflict
0x32ca4db5…4402
0x065c9d…c394
3 touches
1 conflict
0x2b094d69…d033
0x065c9d…c394
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 0xb8b05c3baa…da077c
Audit this contract →
← previous block·next block →recent activity