← previous blocknext block →recent activity
Analyzing
Block #86,811,581
25 transactions · 21 stateful · 2026-07-10 09:28:03 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,811,581 · 25 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
1w05w07w08w19w210w213w314w415w116w017w018w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b79846d…5b19
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e66a473…9fe8
0x34b655…2a6f
4 touches
1 conflict
0x6ba89834…1826
0x34b655…2a6f
4 touches
1 conflict
0x6e6b50c3…9109
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
3 conflicts on slot 0x5b79846d8e…475b19
Audit this contract →
← previous block·next block →recent activity