← previous blocknext block →recent activity
Analyzing
Block #86,808,746
13 transactions · 8 stateful · 2026-07-10 09:09:06 UTC
Parallelism
85/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,808,746 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf090a80…4536
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x6c826b3b…5293
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x10970e1d…90df
0x34b655…2a6f
2 touches
0 conflicts
0x1dd35f86…6627
0x34b655…2a6f
2 touches
0 conflicts
0x24e3bf88…17bf
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: Perpl
1 conflict on slot 0xcf090a809e…b94536
Audit this contract →
← previous block·next block →recent activity