← previous blocknext block →recent activity

Analyzing

Block #86,628,073

19 transactions · 18 stateful · 2026-07-09 13:01:12 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

0.95

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,628,073  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x0c366266…77e1

0x34b655…2a6f

6 touches
3 conflicts

0x1941b441…5889

0x34b655…2a6f

6 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x5b30a6e6…b249

0x34b655…2a6f

6 touches
3 conflicts

0x61c12e81…b215

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xacaba0ad…e266

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

← previous block·next block →recent activity