← previous blocknext block →recent activity
Analyzing
Block #86,779,833
16 transactions · 12 stateful · 2026-07-10 05:56:03 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,779,833 · 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
1w07w09w111w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc282b3d…e139
0x34b655…2a6f
4 touches
1 conflict
0xcf8e671d…080f
0x34b655…2a6f
4 touches
1 conflict
0xfb0fd18f…c895
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x039c2f44…9ac7
0x34b655…2a6f
4 touches
1 conflict
0x69ce640b…884a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
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 0xcc282b3d26…31e139
Audit this contract →
← previous block·next block →recent activity