← previous blocknext block →recent activity
Analyzing
Block #76,351,000
14 transactions · 13 stateful · 2026-05-22 22:27:36 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,351,000 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w312w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xdd4d7901…03f7
0x065c9d…c394
3 touches
1 conflict
0x084de171…d9aa
0x065c9d…c394
3 touches
1 conflict
0xd2b5ebb9…ac5b
0x065c9d…c394
3 touches
1 conflict
0xe6b39798…293b
0x065c9d…c394
3 touches
1 conflict
0x8c8d55de…de47
0x065c9d…c394
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 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity