← previous blocknext block →recent activity
Analyzing
Block #73,483,693
6 transactions · 5 stateful · 2026-05-09 15:22:48 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,483,693 · 6 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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7806279b…3b85
0x065c9d…c394
3 touches
1 conflict
0x12b43234…1b38
0x065c9d…c394
2 touches
0 conflicts
0x20095e1a…3dc3
0x065c9d…c394
2 touches
0 conflicts
0x23f2f31d…1911
0x065c9d…c394
2 touches
0 conflicts
0x6a526192…55a7
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0x9fad79a5…f34c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity