← previous blocknext block →recent activity
Analyzing
Block #73,375,789
12 transactions · 11 stateful · 2026-05-09 03:24:46 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,375,789 · 12 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
1w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x64a4ed59…0daf
0xd32edf…ff58
3 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0xc77c69d4…2c50
0x065c9d…c394
2 touches
0 conflicts
0xce7afaeb…0939
0x065c9d…c394
2 touches
0 conflicts
0xfc23dc3d…1b6a
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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