← previous blocknext block →recent activity
Analyzing
Block #73,967,678
14 transactions · 12 stateful · 2026-05-11 21:20:04 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,967,678 · 14 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
1w03w14w27w28w39w411w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x194f2c02…19e6
0x2a68ba…90c5
4 touches
1 conflict
0x37cfaf01…4a46
0x34b655…2a6f
4 touches
1 conflict
0x37d49489…9309
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x6f08361da9…89bda6
Audit this contract →
← previous block·next block →recent activity