← previous blocknext block →recent activity
Analyzing
Block #73,502,795
10 transactions · 8 stateful · 2026-05-09 17:30:02 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,502,795 · 10 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5fc20e09…0ee7
0x065c9d…c394
4 touches
1 conflict
0xa71e7eec…897a
0x065c9d…c394
3 touches
1 conflict
0xe2d910ce…b45f
0x065c9d…c394
3 touches
1 conflict
0xdf91d78e…1333
0x065c9d…c394
2 touches
0 conflicts
0xe79cfc38…bbbc
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
3 conflicts on slot 0x22e295f5d8…ac1bef
Audit this contract →
← previous block·next block →recent activity