← previous blocknext block →recent activity

Analyzing

Block #87,756,396

24 transactions · 23 stateful · 2026-07-14 18:46:32 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,756,396  ·  24 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

0x5b145de0…367c

0xc8689a…ee79

14 touches
21 conflicts

0x28c62bca…b746

0x34b655…2a6f

14 touches
21 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x747f609d…1555

0x34b655…2a6f

14 touches
21 conflicts

0x9001f549…089d

0x34b655…2a6f

14 touches
21 conflicts

0x9ae859db…2d84

0x34b655…2a6f

14 touches
21 conflicts

0xaa643d44…2122

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

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: Settlement / Helper

21 conflicts on slot 0x5b145de0a2…2e367c

← previous block·next block →recent activity