← previous blocknext block →recent activity

Analyzing

Block #86,708,968

27 transactions · 25 stateful · 2026-07-09 22:02:35 UTC

Parallelism

56/100

Blocked

48%

Avg conflicts / tx

1.41

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #86,708,968  ·  27 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x511ecf07…8ed0

0x34b655…2a6f

8 touches
6 conflicts

0x0d488000…3831

0x34b655…2a6f

8 touches
6 conflicts

0xcc3f7ee8…7924

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

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

10 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity