← previous blocknext block →recent activity
Analyzing
Block #85,513,173
42 transactions · 35 stateful · 2026-07-04 09:00:04 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,513,173 · 42 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
1w02w13w24w35w411w512w513w014w116w217w320w421w522w623w736w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
16 touches
28 conflicts
0xfe577123…c0f8
0xd32edf…ff58
11 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x44d7acbf…e67b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
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: 0x04fdeac2…f747d7
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity