← previous blocknext block →recent activity
Analyzing
Block #73,923,994
9 transactions · 7 stateful · 2026-05-11 16:29:31 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,923,994 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x55d3cdd7…3635
0x065c9d…c394
2 touches
0 conflicts
0x7a4353ee…cc1e
0x065c9d…c394
2 touches
0 conflicts
0x7d2dd0ff…1918
0x065c9d…c394
2 touches
0 conflicts
0x8792fad2…cc72
0x065c9d…c394
2 touches
0 conflicts
0xc8a49b4c…90b7
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity