← previous blocknext block →recent activity
Analyzing
Block #86,250,991
27 transactions · 24 stateful · 2026-07-07 19:00:17 UTC
Parallelism
89/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,250,991 · 27 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
1w02w13w24w05w17w08w113w017w018w119w020w221w124w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34443913…cbf3
0x336ed4…c59c
6 touches
3 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x71f4c564…5b6b
0x34b655…2a6f
4 touches
1 conflict
0x8fb0fecf…cb2f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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: 0x336ed437…cfc59c
3 conflicts on slot 0x3444391364…9ecbf3
Audit this contract →
← previous block·next block →recent activity