← previous blocknext block →recent activity

Analyzing

Block #87,409,149

18 transactions · 17 stateful · 2026-07-13 04:03:21 UTC

Parallelism

56/100

Blocked

53%

Avg conflicts / tx

1.56

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,409,149  ·  18 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

0xa7e2f1b7…7e6f

0x34b655…2a6f

14 touches
21 conflicts

0xb9bc1dfc…6bfb

0x34b655…2a6f

10 touches
10 conflicts

0x1d7140ec…9f87

0x34b655…2a6f

8 touches
6 conflicts

0x286711a5…b3bf

0x34b655…2a6f

8 touches
6 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

8 touches
6 conflicts

0x3f99ec8a…334a

0x34b655…2a6f

8 touches
6 conflicts

0x63c900f4…2600

0x34b655…2a6f

8 touches
6 conflicts

0x727fbce7…0c80

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0xa7e2f1b7f5…cf7e6f

← previous block·next block →recent activity