← previous blocknext block →recent activity
Analyzing
Block #73,868,296
5 transactions · 5 stateful · 2026-05-11 10:18:31 UTC
Parallelism
60/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,868,296 · 5 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95e3fac2…3104
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf439e9f1…0734
0x065c9d…c394
3 touches
1 conflict
0x00b27dce…b787
0x065c9d…c394
2 touches
0 conflicts
0x269e4a33…fdd3
0x065c9d…c394
2 touches
0 conflicts
0x5aa39331…617a
0x065c9d…c394
2 touches
0 conflicts
0x5c6e2a1a…690f
0x065c9d…c394
2 touches
0 conflicts
0x7f81fb82…633e
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 0x95e3fac2f4…973104
Audit this contract →
← previous block·next block →recent activity