← previous blocknext block →recent activity
Analyzing
Block #86,152,385
15 transactions · 14 stateful · 2026-07-07 08:01:46 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,152,385 · 15 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
3w04w16w08w09w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2093058…d36f
0x065c9d…c394
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x340f3b2f…d0be
0x34b655…2a6f
2 touches
0 conflicts
0x456f4453…91f0
0x34b655…2a6f
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 0xf209305884…3ad36f
Audit this contract →
← previous block·next block →recent activity