← previous blocknext block →recent activity
Analyzing
Block #86,635,143
26 transactions · 23 stateful · 2026-07-09 13:48:30 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,635,143 · 26 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
1w02w13w24w35w06w17w09w110w214w215w123w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc88f593e…5d93
0x336ed4…c59c
8 touches
6 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
6 conflicts on slot 0xc88f593e3b…e65d93
Audit this contract →
← previous block·next block →recent activity