pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,499,753
13 transactions · 12 stateful · 2026-05-09 17:09:45 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,499,753 · 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
1w02w13w24w35w06w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xe6bb09fe…e6b6
0x065c9d…c394
4 touches
1 conflict
0x270510d4…f99c
0x065c9d…c394
3 touches
1 conflict
0x0356e7c4…baa1
0x065c9d…c394
3 touches
1 conflict
0x941ffa66…34e6
0x065c9d…c394
2 touches
0 conflicts
0xb953bd34…cbf1
0x065c9d…c394
2 touches
0 conflicts
0xc4959cb2…777e
0x065c9d…c394
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: 0xab35264b…1cfa38
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity