← previous blocknext block →recent activity
Analyzing
Block #86,395,448
15 transactions · 14 stateful · 2026-07-08 11:05:03 UTC
Parallelism
87/100
Blocked
7%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,395,448 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x1f3b2a39…ab2c
0x09475a…400f
2 touches
0 conflicts
0xb1a0dd74…f087
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0002
0x1c8a33…d316
2 touches
0 conflicts
0x919ebc19…0356
0x1c8a33…d316
2 touches
0 conflicts
0xa207048b…6a7e
0x5a66a5…cba8
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