← previous blocknext block →recent activity
Analyzing
Block #86,708,301
15 transactions · 14 stateful · 2026-07-09 21:58:08 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,708,301 · 15 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
5w06w07w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e2685de…dbbe
0x34b655…2a6f
4 touches
1 conflict
0x916f2285…f095
0x34b655…2a6f
4 touches
1 conflict
0x916f2285…f096
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb2fa1675…4e07
0x34b655…2a6f
4 touches
1 conflict
0xbe975635…2b7b
0x34b655…2a6f
4 touches
1 conflict
0xce2f0b6e…0e05
0x34b655…2a6f
4 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
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: Perpl
1 conflict on slot 0x6e2685def9…8edbbe
Audit this contract →
← previous block·next block →recent activity