← previous blocknext block →recent activity
Analyzing
Block #86,713,996
13 transactions · 10 stateful · 2026-07-09 22:36:10 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,713,996 · 13 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef7662…f79b
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xb104db11…2208
0x34b655…2a6f
2 touches
0 conflicts
0x1b374c44…96d9
0x34b655…2a6f
2 touches
0 conflicts
0x226e3b61…5e6f
0x34b655…2a6f
2 touches
0 conflicts
0x3214c052…2036
0x34b655…2a6f
2 touches
0 conflicts
0x38e39eef…50bd
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 0xfaef76626e…4df79b
Audit this contract →
← previous block·next block →recent activity