← previous blocknext block →recent activity
Analyzing
Block #73,991,381
11 transactions · 9 stateful · 2026-05-11 23:59:22 UTC
Parallelism
55/100
Blocked
56%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,991,381 · 11 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
1w03w04w15w26w37w28w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x240b1c62…c966
0x065c9d…c394
2 touches
0 conflicts
0x27a08e35…860c
0x065c9d…c394
2 touches
0 conflicts
0x329248e1…561f
0x065c9d…c394
2 touches
0 conflicts
0x45c8ce08…0271
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