← previous blocknext block →recent activity

Analyzing

Block #87,644,274

19 transactions · 15 stateful · 2026-07-14 06:16:29 UTC

Parallelism

68/100

Blocked

53%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,644,274  ·  19 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

0x08330b36…ae29

0x34b655…2a6f

8 touches
6 conflicts

0x4560e5a8…b741

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x8d4c0bb9…ccd3

0x34b655…2a6f

8 touches
6 conflicts

0xd19c9d38…b459

0x34b655…2a6f

8 touches
6 conflicts

0xed59b1cd…8509

0x34b655…2a6f

8 touches
6 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x49f75237…44f4

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

6 conflicts on slot 0x08330b3687…a7ae29

← previous block·next block →recent activity