← previous blocknext block →recent activity
Analyzing
Block #86,805,287
16 transactions · 14 stateful · 2026-07-10 08:46:01 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,805,287 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w06w17w210w111w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33c7a9e0…4810
0x34b655…2a6f
6 touches
3 conflicts
0xf7ab945c…597e
0x34b655…2a6f
6 touches
3 conflicts
0x01df0928…3426
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x0b320394…cc69
0x34b655…2a6f
6 touches
3 conflicts
0x51ad5401…1eb4
0x34b655…2a6f
4 touches
3 conflicts
0x1586ff62…0ebe
0x34b655…2a6f
4 touches
1 conflict
0x3bca5b95…9ee9
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 0x33c7a9e0fd…4e4810
Audit this contract →
← previous block·next block →recent activity