← previous blocknext block →recent activity
Analyzing
Block #86,758,307
16 transactions · 11 stateful · 2026-07-10 03:32:19 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,758,307 · 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
5w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b1a9a4…0c7f
0x34b655…2a6f
4 touches
1 conflict
0x58f56d50…8887
0x34b655…2a6f
4 touches
1 conflict
0xb7b1a9a4…0c7e
0x34b655…2a6f
4 touches
1 conflict
0xfc4d32c0…39f9
0x34b655…2a6f
4 touches
1 conflict
0xc3a8e1d6…e816
0x34b655…2a6f
4 touches
1 conflict
0xd69bec2a…118e
0x34b655…2a6f
4 touches
1 conflict
0x07202254…c2fd
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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 0xb7b1a9a422…810c7f
Audit this contract →
← previous block·next block →recent activity