← previous blocknext block →recent activity
Analyzing
Block #86,220,603
23 transactions · 20 stateful · 2026-07-07 15:37:15 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,220,603 · 23 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
1w02w13w16w09w210w111w012w213w314w015w418w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x839c0c71…bada
0x34b655…2a6f
6 touches
3 conflicts
0x82d68e46…d52a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
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: MarginAccount
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity