← previous blocknext block →recent activity
Analyzing
Block #76,559,496
9 transactions · 8 stateful · 2026-05-23 21:36:16 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,559,496 · 9 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
1w03w14w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0xe439d57d…c183
0x065c9d…c394
4 touches
1 conflict
0x03add271…5747
0x065c9d…c394
3 touches
1 conflict
0xfffc6698…ceab
0x065c9d…c394
3 touches
1 conflict
0xbb52cb80…6507
0x065c9d…c394
2 touches
0 conflicts
0xef1febcf…4005
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xcc4f1f1446…7caa5f
Audit this contract →
← previous block·next block →recent activity