← previous blocknext block →recent activity
Analyzing
Block #76,222,440
28 transactions · 24 stateful · 2026-05-22 08:11:40 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,222,440 · 28 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
5w06w07w18w210w312w114w017w018w119w221w122w223w426w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
10 touches
10 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
8 touches
6 conflicts
0x0835704a…24c3
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xea57afd0…4232
0x34b655…2a6f
6 touches
3 conflicts
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
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 0xf3d7a307cc…f14d63
Audit this contract →
← previous block·next block →recent activity