← previous blocknext block →recent activity

Analyzing

Block #87,729,950

27 transactions · 23 stateful · 2026-07-14 15:49:39 UTC

Parallelism

67/100

Blocked

52%

Avg conflicts / tx

1.48

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,729,950  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x7e5ea60a…c4aa

0x34b655…2a6f

14 touches
21 conflicts

0x1941b441…5889

0x34b655…2a6f

12 touches
15 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x29d0d77a…7d7b

0x34b655…2a6f

8 touches
6 conflicts

0x312e4698…54c0

0x34b655…2a6f

8 touches
6 conflicts

0x4ca1448c…9de6

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

21 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity