← previous blocknext block →recent activity
Analyzing
Block #86,237,658
20 transactions · 16 stateful · 2026-07-07 17:31:06 UTC
Parallelism
90/100
Blocked
6%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,237,658 · 20 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
1w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4753cecb…e0ee
0x065c9d…c394
2 touches
0 conflicts
0xd1f7b10e…df08
0x065c9d…c394
2 touches
0 conflicts
0xdba12831…56a5
0x065c9d…c394
2 touches
0 conflicts
0xdf40c66b…2e30
0x065c9d…c394
2 touches
0 conflicts
0xefbb8e77…df5d
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