← previous blocknext block →recent activity
Analyzing
Block #85,838,305
14 transactions · 12 stateful · 2026-07-05 21:06:21 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,838,305 · 14 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xbeb13b37…c287
0xd32edf…ff58
3 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x8edd456e…c7e3
0x0555e3…2b9c
2 touches
0 conflicts
0xa554be53…01cc
0x0555e3…2b9c
2 touches
0 conflicts
0x66de0ce3…337a
0x188d58…ea8e
2 touches
0 conflicts
0x66de0ce3…337b
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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: MarginAccount
1 conflict on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity