← previous blocknext block →recent activity
Analyzing
Block #86,820,729
19 transactions · 19 stateful · 2026-07-10 10:29:18 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,820,729 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w310w012w113w416w017w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x9fbc6a76…9c29
0x34b655…2a6f
6 touches
3 conflicts
0xb104db11…2208
0x34b655…2a6f
6 touches
3 conflicts
0xce3de73c…ae35
0x34b655…2a6f
6 touches
3 conflicts
0xce3de73c…ae36
0x34b655…2a6f
6 touches
3 conflicts
0x7ef9f6fb…99c5
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity