← previous blocknext block →recent activity
Analyzing
Block #75,945,495
13 transactions · 10 stateful · 2026-05-21 01:26:55 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,945,495 · 13 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
8w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x14e6f244…cbf0
0x6657d1…8ccc
2 touches
0 conflicts
0x36eaa473…f47c
0x6657d1…8ccc
2 touches
0 conflicts
0x37809ed6…0d6d
0x6657d1…8ccc
2 touches
0 conflicts
0x3e11a0cf…ddcb
0x6657d1…8ccc
2 touches
0 conflicts
0x494df903…f40c
0x6657d1…8ccc
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