← previous blocknext block →recent activity
Analyzing
Block #85,763,233
13 transactions · 11 stateful · 2026-07-05 12:46:23 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,763,233 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xcfd62e58…4a8a
0x065c9d…c394
3 touches
1 conflict
0x98132e34…e130
0x065c9d…c394
3 touches
1 conflict
0xa429f418…8e92
0x40c49f…2af0
2 touches
0 conflicts
0xa848984b…c253
0x40c49f…2af0
2 touches
0 conflicts
0xf743fbe6…94d5
0x40c49f…2af0
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
3 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity