← previous blocknext block →recent activity
Analyzing
Block #86,885,172
15 transactions · 12 stateful · 2026-07-10 17:40:13 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,885,172 · 15 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
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xa8be8896…56b8
0xd32edf…ff58
3 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
2 touches
0 conflicts
0x9a287655…f785
0x34b655…2a6f
2 touches
0 conflicts
0xac388ba5…a800
0x34b655…2a6f
2 touches
0 conflicts
0xf4a27876…b09c
0x34b655…2a6f
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity