← previous blocknext block →recent activity
Analyzing
Block #75,702,438
19 transactions · 16 stateful · 2026-05-19 22:26:57 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,702,438 · 19 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
4w06w07w011w113w014w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xe6dbdcdc…eacc
0x065c9d…c394
4 touches
1 conflict
0x212a7a8e…9bf0
0x065c9d…c394
3 touches
1 conflict
0x1fa3a9d5…fc4b
0xd32edf…ff58
3 touches
1 conflict
0xbd0008eb…362a
0x065c9d…c394
3 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity