← previous blocknext block →recent activity
Analyzing
Block #86,075,706
15 transactions · 11 stateful · 2026-07-06 23:30:03 UTC
Parallelism
87/100
Blocked
9%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,075,706 · 15 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
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4a344ec5…bbd3
0x065c9d…c394
3 touches
1 conflict
0xc8d0a996…3c9c
0x065c9d…c394
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x86cea35b…bdff
0x34b655…2a6f
2 touches
0 conflicts
0x06e40499…165e
0x69df8a…6292
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 0x77ed432f03…d6fa04
Audit this contract →
← previous block·next block →recent activity