← previous blocknext block →recent activity
Analyzing
Block #86,686,856
25 transactions · 19 stateful · 2026-07-09 19:35:06 UTC
Parallelism
84/100
Blocked
37%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,686,856 · 25 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
3w06w07w19w211w312w120w021w122w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa248a5dd…4a69
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3077b286…8304
0x34b655…2a6f
4 touches
1 conflict
0x40287836…2dff
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 0xa248a5dd13…914a69
Audit this contract →
← previous block·next block →recent activity