← previous blocknext block →recent activity

Analyzing

Block #86,681,947

17 transactions · 15 stateful · 2026-07-09 19:02:20 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.12

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,681,947  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x1a5d321d…a474

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x002a0f9e…b33b

0xea1b8e…c5ec

2 touches
0 conflicts

0x0abe35e4…7a17

0xea1b8e…c5ec

2 touches
0 conflicts

0x455b104f…3960

0xea1b8e…c5ec

2 touches
0 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

1 conflict on slot 0x1a5d321d5d…0da474

← previous block·next block →recent activity