← previous blocknext block →recent activity
Analyzing
Block #86,192,685
35 transactions · 30 stateful · 2026-07-07 12:30:47 UTC
Parallelism
86/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,192,685 · 35 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
1w02w18w09w112w113w214w015w116w117w219w020w123w025w226w327w428w033w134w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0x0191a97b…95f1
0xd32edf…ff58
5 touches
3 conflicts
0x6ed985ff…e9ac
0x065c9d…c394
5 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb86
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity