← previous blocknext block →recent activity
Analyzing
Block #86,384,388
17 transactions · 15 stateful · 2026-07-08 09:51:14 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,384,388 · 17 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
1w03w04w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x3147083e…48d9
0x34b655…2a6f
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0x36b18ecf…8517
0x065c9d…c394
2 touches
0 conflicts
0x791ffd42…bc1f
0x065c9d…c394
2 touches
0 conflicts
0xb889c67f…b03b
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