← previous blocknext block →recent activity

Analyzing

Block #86,688,545

19 transactions · 15 stateful · 2026-07-09 19:46:22 UTC

Parallelism

68/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,688,545  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x56b5f5c0…a3ad

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xfc578b53…9b1f

0xa6afd3…d132

4 touches
1 conflict

0x23ef1567…8f31

0x34b655…2a6f

4 touches
1 conflict

0x53cccb07…d7f0

0x34b655…2a6f

4 touches
1 conflict

0xb5cddf91…0abf

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity