pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,986,465
34 transactions · 31 stateful · 2026-04-28 02:02:46 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #70,986,465 · 34 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w19w010w112w013w114w215w317w019w120w121w022w223w324w225w426w530w431w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad68552…e6bf
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x414e9446…4b59
0x34b655…2a6f
6 touches
3 conflicts
0x4db74a88…1c46
0x34b655…2a6f
6 touches
3 conflicts
0x4e39aafd…796e
0x34b655…2a6f
6 touches
3 conflicts
0x904fc3c0…00ec
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xbad6855239…f0e6bf
Audit this contract →
← previous block·next block →recent activity