← previous blocknext block →recent activity

Analyzing

Block #86,225,391

23 transactions · 15 stateful · 2026-07-07 16:09:13 UTC

Parallelism

83/100

Blocked

47%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,225,391  ·  23 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x07d8b1e8…78c6

0x34b655…2a6f

4 touches
1 conflict

0x2c2761c0…476e

0x34b655…2a6f

4 touches
1 conflict

0x476eb96a…347d

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x502b2bfa…410b

0x34b655…2a6f

4 touches
1 conflict

0x5d1ac445…5233

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: Perpl

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity