← previous blocknext block →recent activity
Analyzing
Block #86,819,195
20 transactions · 16 stateful · 2026-07-10 10:18:57 UTC
Parallelism
80/100
Blocked
19%
Avg conflicts / tx
0.15
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,819,195 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w113w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a36d0c8…12e2
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e3
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xb3ae4660…5f75
0x34b655…2a6f
4 touches
1 conflict
0xb7a47e62…7963
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xc92cdb89…7078
0x34b655…2a6f
4 touches
1 conflict
0xc948dbdc…199a
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 0x5a36d0c873…e212e2
Audit this contract →
← previous block·next block →recent activity