← previous blocknext block →recent activity

Analyzing

Block #87,317,292

18 transactions · 17 stateful · 2026-07-12 17:49:01 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,317,292  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0xf79472ee…c820

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x7e5ea60a…c4a4

0x34b655…2a6f

4 touches
1 conflict

0x88ad4557…bd8d

0x34b655…2a6f

4 touches
1 conflict

0x8e7e9235…01bb

0x34b655…2a6f

4 touches
1 conflict

0x8e7e9235…01bc

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xc36fa35805…6f24cb

← previous block·next block →recent activity