pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,923,208
10 transactions · 10 stateful · 2026-04-27 19:01:27 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,923,208 · 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
1w02w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
0xc87e52aa…3593
0x065c9d…c394
4 touches
1 conflict
0x6e2b2f4b…558c
0x065c9d…c394
4 touches
1 conflict
0x8a35acfb…d1b0
0x8d66a4…3095
4 touches
1 conflict
0x54bfda47…ba88
0x065c9d…c394
3 touches
1 conflict
0x558db9e3…96a0
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: 0xd0f8a642…83badc
1 conflict on slot 0x0000000000…000004
Audit this contract →
← previous block·next block →recent activity