← previous blocknext block →recent activity

Analyzing

Block #86,103,389

23 transactions · 20 stateful · 2026-07-07 02:34:38 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

0.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,103,389  ·  23 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

8 touches
6 conflicts

0x4c619b7d…f4fa

0x34b655…2a6f

8 touches
6 conflicts

0x6da49392…3791

0x34b655…2a6f

6 touches
3 conflicts

0xc400ddde…e754

0x34b655…2a6f

6 touches
3 conflicts

0xfefb0189…f726

0x34b655…2a6f

6 touches
3 conflicts

0xb1c67a7d…b9b1

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc857b971…0bcf

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity