← previous blocknext block →recent activity
Analyzing
Block #86,619,455
40 transactions · 34 stateful · 2026-07-09 12:03:42 UTC
Parallelism
88/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,619,455 · 40 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
5w06w17w010w211w312w013w114w215w316w217w118w225w328w330w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81c55d0e…f4b9
0x065c9d…c394
9 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x8ad1aa01…99d9
0xd32edf…ff58
7 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x81c55d0e89…23f4b9
Audit this contract →
← previous block·next block →recent activity