← previous blocknext block →recent activity

Analyzing

Block #87,078,316

19 transactions · 18 stateful · 2026-07-11 15:10:40 UTC

Parallelism

63/100

Blocked

56%

Avg conflicts / tx

1.37

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,078,316  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x92385428…6941

0x34b655…2a6f

12 touches
15 conflicts

0x0733be30…112f

0x34b655…2a6f

10 touches
10 conflicts

0xf60062ab…f98c

0x34b655…2a6f

6 touches
3 conflicts

0xfaf3835b…98c7

0x34b655…2a6f

6 touches
3 conflicts

0x266a6b2c…4376

0x34b655…2a6f

6 touches
3 conflicts

0x266a6b2c…4377

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x489646ad…1521

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

15 conflicts on slot 0x92385428ad…dc6941

← previous block·next block →recent activity