← previous blocknext block →recent activity

Analyzing

Block #87,735,645

22 transactions · 21 stateful · 2026-07-14 16:27:44 UTC

Parallelism

50/100

Blocked

57%

Avg conflicts / tx

1.27

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #87,735,645  ·  22 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

0x9001f549…089d

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x11b20d84…4c52

0x34b655…2a6f

6 touches
3 conflicts

0x22e7ebfe…1293

0x34b655…2a6f

6 touches
3 conflicts

0x26050074…6967

0x34b655…2a6f

6 touches
3 conflicts

0x58620f29…db5a

0x34b655…2a6f

6 touches
3 conflicts

0x5b145de0…367c

0xc8689a…ee79

6 touches
3 conflicts

0x077d58c3…8ed7

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 0x9001f5497d…54089d

← previous block·next block →recent activity