← previous blocknext block →recent activity
Analyzing
Block #75,989,825
17 transactions · 9 stateful · 2026-05-21 06:22:08 UTC
Parallelism
88/100
Blocked
11%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,989,825 · 17 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
1w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b49d8da…3511
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0xbe70471a…f713
0x065c9d…c394
3 touches
1 conflict
0xfa72a635…6835
0x065c9d…c394
3 touches
1 conflict
0xa7923377…a0dc
0x065c9d…c394
2 touches
0 conflicts
0xd777df23…bbeb
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 0x9b49d8dab1…a93511
Audit this contract →
← previous block·next block →recent activity