pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,092,536
34 transactions · 32 stateful · 2026-04-28 13:49:05 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.79
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #71,092,536 · 34 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w010w111w212w313w214w317w418w519w420w621w722w824w826w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
16 touches
28 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x47b807a2…3307
0x065c9d…c394
10 touches
10 conflicts
0x41755291…977f
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x131a2e…0da9
8 touches
6 conflicts
0x41755291…977f
0x131a2e…0da9
8 touches
6 conflicts
0x4ab14837…e1b2
0x2a68ba…90c5
8 touches
6 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: 0x2a68ba18…8e90c5
28 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity