← previous blocknext block →recent activity

Analyzing

Block #87,732,820

26 transactions · 23 stateful · 2026-07-14 16:08:51 UTC

Parallelism

65/100

Blocked

48%

Avg conflicts / tx

1.65

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,732,820  ·  26 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

0x6fe7d366…78ff

0x34b655…2a6f

16 touches
28 conflicts

0xa55c4598…2988

0x34b655…2a6f

10 touches
10 conflicts

0x805d08cf…3cfc

0x34b655…2a6f

8 touches
6 conflicts

0xdfbd8991…5bd1

0x34b655…2a6f

8 touches
6 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

8 touches
6 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x3726966a…669d

0x34b655…2a6f

8 touches
6 conflicts

0x2d7ea048…d78e

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

28 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity