← previous blocknext block →recent activity
Analyzing
Block #86,960,941
31 transactions · 24 stateful · 2026-07-11 02:06:38 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,960,941 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w18w211w315w016w317w018w021w122w123w424w529w030w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xa3572541…5f75
0xd32edf…ff58
7 touches
6 conflicts
0xe01158fd…f982
0x1b6862…e19c
6 touches
3 conflicts
0x4681609f…6493
0x34b655…2a6f
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity