← previous blocknext block →recent activity
Analyzing
Block #73,967,600
9 transactions · 7 stateful · 2026-05-11 21:19:33 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,967,600 · 9 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
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x34164c7c…2f25
0x065c9d…c394
4 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0xc95a2e54…3630
0x065c9d…c394
3 touches
1 conflict
0x9c4bda7c…533d
0x065c9d…c394
3 touches
1 conflict
0x878d6974…ff7a
0x065c9d…c394
2 touches
0 conflicts
0xb57b365e…70ed
0x065c9d…c394
2 touches
0 conflicts
0xda4cc9ae…3ff3
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