← previous blocknext block →recent activity

Analyzing

Block #87,878,538

33 transactions · 30 stateful · 2026-07-15 08:23:32 UTC

Parallelism

67/100

Blocked

57%

Avg conflicts / tx

2.06

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #87,878,538  ·  33 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

0xd98b3c10…67b8

0x34b655…2a6f

18 touches
36 conflicts

0xd972ea45…48b5

0x34b655…2a6f

14 touches
21 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0xfe2c1082…db16

0x34b655…2a6f

8 touches
6 conflicts

0x0dd44476…ef40

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x4cee015b…1a5e

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity