← previous blocknext block →recent activity
Analyzing
Block #86,075,207
27 transactions · 23 stateful · 2026-07-06 23:26:44 UTC
Parallelism
93/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,075,207 · 27 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
1w010w012w116w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9c9bd18f…fe79
0x065c9d…c394
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x9926140d…8cc2
0x065c9d…c394
3 touches
1 conflict
0xfefca6b2…2f1f
0x065c9d…c394
3 touches
1 conflict
0x204f9e84…7338
0xd32edf…ff58
3 touches
1 conflict
0x5b3b7d9f…fa52
0x3c2269…cf62
2 touches
0 conflicts
0x81d67c49…e69c
0x3c2269…cf62
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