← previous blocknext block →recent activity
Analyzing
Block #73,652,320
14 transactions · 11 stateful · 2026-05-10 10:06:45 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,652,320 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f6d98a3…5ea6
0x34b655…2a6f
6 touches
3 conflicts
0x38524fae…9deb
0x34b655…2a6f
6 touches
3 conflicts
0xc34a0420…db6a
0x34b655…2a6f
6 touches
3 conflicts
0xf2438038…5fa7
0x34b655…2a6f
6 touches
3 conflicts
0xa4491162…f34b
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
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: Perpl
3 conflicts on slot 0x2f6d98a32e…e15ea6
Audit this contract →
← previous block·next block →recent activity