← previous blocknext block →recent activity
Analyzing
Block #86,076,914
13 transactions · 12 stateful · 2026-07-06 23:38:05 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,076,914 · 13 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
1w06w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1cffd0d8…54ea
0x065c9d…c394
2 touches
0 conflicts
0x544e0616…4f0f
0x065c9d…c394
2 touches
0 conflicts
0x8934d3f1…cca9
0x065c9d…c394
2 touches
0 conflicts
0xa58f9a98…243e
0x065c9d…c394
2 touches
0 conflicts
0xd2d681e1…8644
0x065c9d…c394
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 0x95523e2aaf…734c01
Audit this contract →
← previous block·next block →recent activity