← previous blocknext block →recent activity

Analyzing

Block #87,595,102

19 transactions · 18 stateful · 2026-07-14 00:47:44 UTC

Parallelism

53/100

Blocked

56%

Avg conflicts / tx

1.32

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,595,102  ·  19 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd93edb3f…94ec

0x34b655…2a6f

12 touches
15 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x26050074…6967

0x34b655…2a6f

8 touches
6 conflicts

0xd11dcf4e…518f

0x34b655…2a6f

8 touches
6 conflicts

0xd19c9d38…b459

0x34b655…2a6f

8 touches
6 conflicts

0xd8675136…9a01

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

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

15 conflicts on slot 0xd93edb3f20…0394ec

← previous block·next block →recent activity