← previous blocknext block →recent activity

Analyzing

Block #87,704,663

31 transactions · 28 stateful · 2026-07-14 13:00:18 UTC

Parallelism

65/100

Blocked

54%

Avg conflicts / tx

1.74

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #87,704,663  ·  31 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

18 touches
36 conflicts

0x8fe37a3f…4c89

0x34b655…2a6f

10 touches
10 conflicts

0x4560e5a8…b741

0x34b655…2a6f

8 touches
6 conflicts

0x67905f6e…02a1

0x34b655…2a6f

8 touches
6 conflicts

0x6b0d2ce5…ff19

0x34b655…2a6f

8 touches
6 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x214fb529…3f33

0x34b655…2a6f

8 touches
6 conflicts

0xdc8d4ee0…def3

0x34b655…2a6f

8 touches
6 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

36 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity