← previous blocknext block →recent activity
Analyzing
Block #86,055,015
28 transactions · 18 stateful · 2026-07-06 21:12:04 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,055,015 · 28 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
1w06w07w111w012w114w015w117w018w219w220w321w425w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61377ba1…0bef
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x40b8f0ac…20bb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x743add2d…cfbe
0x34b655…2a6f
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-WETH/USDC
3 conflicts on slot 0x61377ba1ed…160bef
Audit this contract →
← previous block·next block →recent activity