← previous blocknext block →recent activity
Analyzing
Block #75,678,625
6 transactions · 5 stateful · 2026-05-19 19:48:54 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,678,625 · 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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x997a616a…7b81
0x065c9d…c394
3 touches
1 conflict
0xb074024f…6127
0x065c9d…c394
3 touches
1 conflict
0x5c3e4fbc…8f9c
0x065c9d…c394
2 touches
0 conflicts
0x60e17a1b…a245
0x065c9d…c394
2 touches
0 conflicts
0x73c4377b…98a6
0x065c9d…c394
2 touches
0 conflicts
0xa33f916f…e3ab
0x065c9d…c394
2 touches
0 conflicts
0xa46987d9…efd1
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity