← previous blocknext block →recent activity
Analyzing
Block #86,353,360
13 transactions · 12 stateful · 2026-07-08 06:23:44 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,353,360 · 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
3w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x69bb3cb2…222d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5d490cba…2724
0x065c9d…c394
3 touches
1 conflict
0x872e1b81…de7a
0x065c9d…c394
3 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x34c408a4…1f20
0x34b655…2a6f
2 touches
0 conflicts
0x51b956b6…1e3f
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 0x49cbdb1b43…f7bda4
Audit this contract →
← previous block·next block →recent activity