← previous blocknext block →recent activity

Analyzing

Block #87,304,287

17 transactions · 16 stateful · 2026-07-12 16:22:03 UTC

Parallelism

53/100

Blocked

63%

Avg conflicts / tx

1.24

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,304,287  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xa05444cf…cd70

0x34b655…2a6f

8 touches
6 conflicts

0x3ef0952c…762d

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x1067498b…53a5

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09c

0x34b655…2a6f

4 touches
1 conflict

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 0xa05444cff4…1ecd70

← previous block·next block →recent activity