← previous blocknext block →recent activity
Analyzing
Block #75,910,948
6 transactions · 4 stateful · 2026-05-20 21:37:00 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,910,948 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0eb00a42…8473
0x065c9d…c394
2 touches
0 conflicts
0x5e6379a4…bfcd
0x065c9d…c394
2 touches
0 conflicts
0x8325a3f5…42ef
0x065c9d…c394
2 touches
0 conflicts
0xef21170a…a2a5
0x065c9d…c394
2 touches
0 conflicts
0xf2636932…a43f
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 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity