← previous blocknext block →recent activity

Analyzing

Block #87,727,560

33 transactions · 27 stateful · 2026-07-14 15:33:40 UTC

Parallelism

64/100

Blocked

56%

Avg conflicts / tx

1.36

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #87,727,560  ·  33 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

14 touches
21 conflicts

0xc4de6652…13f4

0x34b655…2a6f

10 touches
10 conflicts

0x67905f6e…02a1

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

8 touches
6 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x32ab355b…e143

0x34b655…2a6f

8 touches
6 conflicts

0x84d74093…7808

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

21 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity