← previous blocknext block →recent activity
Analyzing
Block #86,816,642
17 transactions · 16 stateful · 2026-07-10 10:01:53 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,816,642 · 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
1w02w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9040c7dc…eac5
0x34b655…2a6f
4 touches
1 conflict
0xc857b971…0bcf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0xe2c559d1…573e
0xd32edf…ff58
3 touches
1 conflict
0x0a5a4598…01bc
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
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 0x9040c7dcfe…1ceac5
Audit this contract →
← previous block·next block →recent activity