← previous blocknext block →recent activity

Analyzing

Block #87,751,198

21 transactions · 21 stateful · 2026-07-14 18:11:48 UTC

Parallelism

52/100

Blocked

52%

Avg conflicts / tx

1.24

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,751,198  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x3e644b16…807b

0x34b655…2a6f

6 touches
3 conflicts

0x2d7ea048…d78e

0x34b655…2a6f

6 touches
3 conflicts

0xaa99c369…263d

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

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