← previous blocknext block →recent activity

Analyzing

Block #87,708,069

28 transactions · 23 stateful · 2026-07-14 13:23:06 UTC

Parallelism

53/100

Blocked

57%

Avg conflicts / tx

2.11

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #87,708,069  ·  28 txs across 13 waves  ·  depth 13
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

wave w12

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

20 touches
45 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x366f651e…6100

0x34b655…2a6f

8 touches
6 conflicts

0x50718952…7c75

0x34b655…2a6f

8 touches
6 conflicts

0x36b7c966…ba5c

0x34b655…2a6f

8 touches
6 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

8 touches
6 conflicts

0x7525206c…fbd5

0x34b655…2a6f

8 touches
6 conflicts

0xa3c36de0…3cf3

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

45 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity