← previous blocknext block →recent activity
Analyzing
Block #73,383,309
11 transactions · 8 stateful · 2026-05-09 04:14:45 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,383,309 · 11 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb159af88…a9e7
0x065c9d…c394
4 touches
1 conflict
0x0711ec2d…d973
0x34b655…2a6f
2 touches
0 conflicts
0x14845934…d13c
0x34b655…2a6f
2 touches
0 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
2 touches
0 conflicts
0x2a4146fa…ab95
0x34b655…2a6f
2 touches
0 conflicts
0x4f483049…3cc7
0x34b655…2a6f
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity