← previous blocknext block →recent activity
Analyzing
Block #86,686,169
16 transactions · 14 stateful · 2026-07-09 19:30:31 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,686,169 · 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
6w07w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0xddbb53a9…9198
0x34b655…2a6f
4 touches
1 conflict
0xffcb5f20…df5a
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x11b186b3…1e48
0x34b655…2a6f
4 touches
1 conflict
0x1b185f7c…4d44
0x34b655…2a6f
4 touches
1 conflict
0x31ec17e3…8912
0x34b655…2a6f
4 touches
1 conflict
0x31ec17e3…8913
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 0xd79c972734…f71233
Audit this contract →
← previous block·next block →recent activity