← previous blocknext block →recent activity
Analyzing
Block #86,075,233
12 transactions · 10 stateful · 2026-07-06 23:26:55 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,075,233 · 12 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
1w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb5dd43…b199
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd8ea0a6b…7ba4
0x065c9d…c394
3 touches
1 conflict
0x59b74223…532f
0x065c9d…c394
2 touches
0 conflicts
0x1c912a68…3b21
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0xafd867b7…2b2e
0x34b655…2a6f
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 0xfcb5dd43dc…bcb199
Audit this contract →
← previous block·next block →recent activity