← previous blocknext block →recent activity

Analyzing

Block #87,262,116

22 transactions · 18 stateful · 2026-07-12 11:40:08 UTC

Parallelism

73/100

Blocked

39%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,262,116  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x5cebb016…c149

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x22c2bb0c…9d5d

0x34b655…2a6f

6 touches
3 conflicts

0x16649a8b…40b0

0x34b655…2a6f

6 touches
3 conflicts

0x16649a8b…40b1

0x34b655…2a6f

6 touches
3 conflicts

0x732d520d…c5f9

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 0x737acb7813…fafce8

← previous block·next block →recent activity