← previous blocknext block →recent activity

Analyzing

Block #86,696,337

20 transactions · 18 stateful · 2026-07-09 20:38:18 UTC

Parallelism

60/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,696,337  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x8f1f40f7…a6a0

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0xb13b96bd…a3cb

0x34b655…2a6f

6 touches
3 conflicts

0xb678410a…0edb

0x34b655…2a6f

6 touches
3 conflicts

0xc6d08d8c…2b98

0x34b655…2a6f

6 touches
3 conflicts

0xd1ec0dfd…ccc0

0xc8689a…ee79

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

6 conflicts on slot 0x8f1f40f78a…78a6a0

← previous block·next block →recent activity