pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,348,612
35 transactions · 30 stateful · 2026-05-09 00:24:00 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
0.97
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,348,612 · 35 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w18w210w313w215w016w117w218w319w420w522w225w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x64403d10…3ac6
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x0a85a226…83bf
0x1b6862…e19c
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: 0xab35264b…1cfa38
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity