pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,995,431
5 transactions · 5 stateful · 2026-04-28 03:02:30 UTC
Parallelism
60/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,995,431 · 5 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xbf009927…c633
0x065c9d…c394
4 touches
1 conflict
0xf4bdcf41…b8b4
0x065c9d…c394
4 touches
1 conflict
0x15376a64…f87d
0x065c9d…c394
4 touches
1 conflict
0x28b2b229…15cd
0x065c9d…c394
4 touches
1 conflict
0x9a2c5f48…84c6
0x065c9d…c394
2 touches
1 conflict
0x9a2c5f48…84c7
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity