← previous blocknext block →recent activity
Analyzing
Block #86,300,089
11 transactions · 9 stateful · 2026-07-08 00:27:53 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,300,089 · 11 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
1w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x0c2f6423…d576
0x065c9d…c394
2 touches
0 conflicts
0x1a039cfd…3f0d
0x065c9d…c394
2 touches
0 conflicts
0x377e1c8a…c860
0x065c9d…c394
2 touches
0 conflicts
0x68397ef4…16f5
0x065c9d…c394
2 touches
0 conflicts
0x9a6fa522…cb89
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity