← previous blocknext block →recent activity

Analyzing

Block #86,735,530

23 transactions · 20 stateful · 2026-07-10 01:00:03 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,735,530  ·  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

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x29bc4bda…3617

0x34b655…2a6f

4 touches
1 conflict

0x2b3345cb…cb6b

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5268ce27…cd4b

0x34b655…2a6f

4 touches
1 conflict

0x94b46bd0…e95d

0x34b655…2a6f

4 touches
1 conflict

0xa08f40b2…9a93

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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity