← previous blocknext block →recent activity
Analyzing
Block #73,705,868
8 transactions · 5 stateful · 2026-05-10 16:08:04 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,705,868 · 8 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
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0xea0b0ba6…30f7
0x065c9d…c394
3 touches
1 conflict
0x23e1a513…fc25
0x065c9d…c394
2 touches
0 conflicts
0x4fe264b9…5d21
0x065c9d…c394
2 touches
0 conflicts
0x8d85281c…1e31
0x065c9d…c394
2 touches
0 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
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 0x529acb6ad1…f0fcc6
Audit this contract →
← previous block·next block →recent activity