← previous blocknext block →recent activity
Analyzing
Block #73,867,942
9 transactions · 7 stateful · 2026-05-11 10:16:09 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,867,942 · 9 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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc769e4fb…ac14
0x065c9d…c394
4 touches
1 conflict
0xc8c35291…7342
0x065c9d…c394
4 touches
1 conflict
0x0969ae39…6119
0x065c9d…c394
2 touches
0 conflicts
0x121e7300…862a
0x065c9d…c394
2 touches
0 conflicts
0x266cccac…89c7
0x065c9d…c394
2 touches
0 conflicts
0x3985a3aa…5dce
0x065c9d…c394
2 touches
0 conflicts
0xb659fc18…61f5
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity