← previous blocknext block →recent activity
Analyzing
Block #86,734,044
16 transactions · 11 stateful · 2026-07-10 00:50:08 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,734,044 · 16 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
1w05w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x81dbafca…d1ea
0x851145…3f07
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 conflicts
0x28387633…e029
0x34b655…2a6f
2 touches
0 conflicts
0x46e3da6b…72ca
0x34b655…2a6f
2 touches
0 conflicts
0x7b44c37c…6fc8
0x34b655…2a6f
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 0xd35bb5ac3f…003586
Audit this contract →
← previous block·next block →recent activity