pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,389,258
13 transactions · 13 stateful · 2026-05-09 04:54:21 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,389,258 · 13 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
2w03w14w25w37w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa3e5ab2…fd8a
0x3bd359…433a
8 touches
6 conflicts
0xd46cd782…e7f2
0x7131ec…7777
8 touches
6 conflicts
0x00000000…0000
0xc82b5c…bb3a
8 touches
6 conflicts
0x00000000…0002
0xc82b5c…bb3a
8 touches
6 conflicts
0x00000000…0003
0xc82b5c…bb3a
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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: 0x3bd359c1…15433a
6 conflicts on slot 0xaa3e5ab2a1…b6fd8a
Audit this contract →
← previous block·next block →recent activity