← previous blocknext block →recent activity
Analyzing
Block #86,776,075
17 transactions · 14 stateful · 2026-07-10 05:30:58 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,776,075 · 17 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
3w04w16w17w210w311w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x97bc6b5d…55ca
0x34b655…2a6f
6 touches
3 conflicts
0xe60e9000…c058
0x34b655…2a6f
6 touches
3 conflicts
0xa84e1c73…0c49
0x34b655…2a6f
4 touches
1 conflict
0xba4d47a9…0d84
0x34b655…2a6f
4 touches
1 conflict
0xe04e9d60…bbef
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