← previous blocknext block →recent activity
Analyzing
Block #85,162,378
22 transactions · 21 stateful · 2026-07-02 18:03:56 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,162,378 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47d4745e…02bb
0x336ed4…c59c
16 touches
28 conflicts
0x00000000…000a
0x90c374…be45
16 touches
28 conflicts
0x00000000…000b
0x90c374…be45
16 touches
28 conflicts
0x34443913…cbf3
0x336ed4…c59c
10 touches
10 conflicts
0x4a870d86…79ef
0x336ed4…c59c
10 touches
10 conflicts
0xc88f593e…5d93
0x336ed4…c59c
6 touches
3 conflicts
0x93c58e4d…9b32
0x336ed4…c59c
6 touches
3 conflicts
0x7fffd49d…772a
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
28 conflicts on slot 0x47d4745e02…9002bb
Audit this contract →
← previous block·next block →recent activity