← previous blocknext block →recent activity
Analyzing
Block #76,445,797
8 transactions · 7 stateful · 2026-05-23 08:59:01 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,445,797 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ba9bc3a…aded
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x86591dfe…b325
0x065c9d…c394
3 touches
1 conflict
0xd748563c…ae8f
0x065c9d…c394
2 touches
0 conflicts
0xded9b78f…5d1f
0x065c9d…c394
2 touches
0 conflicts
0xff5133ac…b7d8
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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
1 conflict on slot 0x0ba9bc3a06…39aded
Audit this contract →
← previous block·next block →recent activity