← previous blocknext block →recent activity

Analyzing

Block #87,735,487

19 transactions · 19 stateful · 2026-07-14 16:26:41 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

1.11

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,735,487  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x22e7ebfe…1293

0x34b655…2a6f

6 touches
3 conflicts

0x26050074…6967

0x34b655…2a6f

6 touches
3 conflicts

0x5b145de0…367c

0xc8689a…ee79

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x58620f29…db5a

0x34b655…2a6f

6 touches
3 conflicts

0x7a2c83a3…a29a

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity