← previous blocknext block →recent activity

Analyzing

Block #87,713,048

21 transactions · 19 stateful · 2026-07-14 13:56:25 UTC

Parallelism

62/100

Blocked

53%

Avg conflicts / tx

1.48

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,713,048  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0xa6389d47…9a28

0x34b655…2a6f

12 touches
15 conflicts

0x5b145de0…367c

0xc8689a…ee79

10 touches
10 conflicts

0x53bddbe8…2e5e

0x34b655…2a6f

10 touches
10 conflicts

0x67905f6e…02a1

0x34b655…2a6f

10 touches
10 conflicts

0xd11dcf4e…518f

0x34b655…2a6f

10 touches
10 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

10 touches
10 conflicts

0x7f925d18…0689

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

15 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity