← previous blocknext block →recent activity

Analyzing

Block #86,453,674

22 transactions · 18 stateful · 2026-07-08 17:34:00 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,453,674  ·  22 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

0x8eb0ac6b…a73a

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7ce93f3d…b70e

0x34b655…2a6f

6 touches
3 conflicts

0x130b8bf2…8fd7

0x34b655…2a6f

4 touches
1 conflict

0x211d520a…bf67

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x24534f9b…ccd8

0x34b655…2a6f

4 touches
1 conflict

0x31f5fdff…1604

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 0x8eb0ac6bf2…4da73a

← previous block·next block →recent activity