pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,995,745
14 transactions · 13 stateful · 2026-04-28 03:04:36 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,995,745 · 14 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
5w07w19w010w111w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0001
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0000
0x8fd63a…536c
4 touches
1 conflict
0x8a85cf3d…2868
0x34b655…2a6f
4 touches
1 conflict
0x9dc9fa5f…7f23
0x34b655…2a6f
4 touches
1 conflict
0x67d1a88c…728c
0xd32edf…ff58
3 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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: 0x34b6552d…112a6f
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity