pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,070,197
16 transactions · 14 stateful · 2026-04-28 11:20:12 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,070,197 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa80ab415…55db
0xd32edf…ff58
7 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0xd56db188…ecd0
0x000000…012a
2 touches
0 conflicts
0x56a919c4…ab49
0x01bff4…1071
2 touches
0 conflicts
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0x703b861a…cbe3
0x188d58…ea8e
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: 0xd32edf66…9fff58
6 conflicts on slot 0xa80ab41504…4c55db
Audit this contract →
← previous block·next block →recent activity