← previous blocknext block →recent activity
Analyzing
Block #75,936,540
6 transactions · 5 stateful · 2026-05-21 00:27:14 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,936,540 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x354d90d6…b01e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0df0caf4…f87b
0x065c9d…c394
3 touches
1 conflict
0x4f925e29…1df8
0x065c9d…c394
2 touches
0 conflicts
0x5c748f34…9957
0x065c9d…c394
2 touches
0 conflicts
0xf5f9685c…43ab
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
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 0x354d90d66a…44b01e
Audit this contract →
← previous block·next block →recent activity