← previous blocknext block →recent activity

Analyzing

Block #87,725,358

22 transactions · 17 stateful · 2026-07-14 15:18:54 UTC

Parallelism

68/100

Blocked

53%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,725,358  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x0dd44476…ef40

0x34b655…2a6f

8 touches
6 conflicts

0x0c20b123…6e84

0x34b655…2a6f

6 touches
3 conflicts

0x0d42a59b…df19

0x34b655…2a6f

6 touches
3 conflicts

0x5eb5d9be…b2c1

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x9eb155db…f714

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity