← previous blocknext block →recent activity
Analyzing
Block #86,082,588
30 transactions · 25 stateful · 2026-07-07 00:15:50 UTC
Parallelism
87/100
Blocked
52%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,082,588 · 30 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
1w02w13w25w06w17w28w39w316w317w018w119w220w221w322w327w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47d4745e…02bb
0x336ed4…c59c
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0x75b286f8…d8db
0xd32edf…ff58
7 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xc88f593e…5d93
0x336ed4…c59c
6 touches
3 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 conflicts
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: 0x336ed437…cfc59c
6 conflicts on slot 0x47d4745e02…9002bb
Audit this contract →
← previous block·next block →recent activity