← previous blocknext block →recent activity
Analyzing
Block #73,223,588
10 transactions · 9 stateful · 2026-05-08 10:32:18 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,223,588 · 10 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
1w03w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x7f430e47…4cbd
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0x3f63b02c…1b0e
0x065c9d…c394
2 touches
0 conflicts
0x6e6ec736…78b3
0x065c9d…c394
2 touches
0 conflicts
0x85bf2e56…c785
0x065c9d…c394
2 touches
0 conflicts
0xa3c68c9e…2911
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0b390c6160…02dc07
Audit this contract →
← previous block·next block →recent activity