← previous blocknext block →recent activity
Analyzing
Block #76,527,284
10 transactions · 8 stateful · 2026-05-23 18:01:34 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,527,284 · 10 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
2w03w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26dad84e…9f13
0x065c9d…c394
4 touches
1 conflict
0x6f24c394…3fc3
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaf74cb6d…56ab
0x5afd3e…7620
2 touches
0 conflicts
0xc5416b5c…5fba
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x3378e8b6…20a9
0x754704…b603
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 0x26dad84e68…aa9f13
Audit this contract →
← previous block·next block →recent activity