pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,348,458
16 transactions · 14 stateful · 2026-05-09 00:22:59 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,348,458 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f9b918b…212d
0x34b655…2a6f
4 touches
1 conflict
0x59291da0…a7f7
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
0x1956cea3…dc45
0x34b655…2a6f
4 touches
1 conflict
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
1 conflict on slot 0x0f9b918b6f…1d212d
Audit this contract →
← previous block·next block →recent activity