← previous blocknext block →recent activity
Analyzing
Block #86,703,447
14 transactions · 10 stateful · 2026-07-09 21:25:45 UTC
Parallelism
86/100
Blocked
10%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,703,447 · 14 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
4w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8f6f7a3…f564
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc8f6f7a3…f563
0x34b655…2a6f
4 touches
1 conflict
0xdad3be8c…a703
0x34b655…2a6f
4 touches
1 conflict
0xf23e15be…1749
0x34b655…2a6f
4 touches
1 conflict
0x6e1756b9…40d5
0x34b655…2a6f
3 touches
1 conflict
0xfe352b20…b46c
0x34b655…2a6f
3 touches
1 conflict
0x2cebbc04…8b01
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 0xc8f6f7a3f3…78f564
Audit this contract →
← previous block·next block →recent activity