← previous blocknext block →recent activity
Analyzing
Block #85,983,065
24 transactions · 22 stateful · 2026-07-06 13:11:22 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,983,065 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w08w19w210w311w012w113w114w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0xa41aa077…b81e
0x065c9d…c394
4 touches
2 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity