← previous blocknext block →recent activity
Analyzing
Block #86,126,777
9 transactions · 7 stateful · 2026-07-07 05:10:48 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,126,777 · 9 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
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xfc66fe01…47d7
0x34b655…2a6f
3 touches
1 conflict
0x4973937a…2ae2
0x34b655…2a6f
3 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
2 touches
0 conflicts
0x1ed8510f…3610
0x34b655…2a6f
2 touches
0 conflicts
0x272237d0…47a2
0x34b655…2a6f
2 touches
0 conflicts
0x2fb80aae…a042
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 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity