← previous blocknext block →recent activity
Analyzing
Block #86,789,962
17 transactions · 13 stateful · 2026-07-10 07:03:35 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,789,962 · 17 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
4w07w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3688185…9b36
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0x7b2f3e6d…978f
0x34b655…2a6f
4 touches
1 conflict
0x4caf91f9…8ab5
0x34b655…2a6f
2 touches
0 conflicts
0x65e795ca…0320
0x34b655…2a6f
2 touches
0 conflicts
0x6d99ac64…0aa3
0x34b655…2a6f
2 touches
0 conflicts
0x89aae5a8…e220
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 0xc36881859a…c49b36
Audit this contract →
← previous block·next block →recent activity