← previous blocknext block →recent activity
Analyzing
Block #73,807,737
10 transactions · 9 stateful · 2026-05-11 03:35:06 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,807,737 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2dac298f…32c1
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xc62b2541…79f5
0x065c9d…c394
3 touches
1 conflict
0x411fd21d…9dd7
0x065c9d…c394
2 touches
0 conflicts
0x875cdf1c…ee88
0x065c9d…c394
2 touches
0 conflicts
0xbebcf6cf…1756
0x065c9d…c394
2 touches
0 conflicts
0xc818cb3d…1a40
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity