← previous blocknext block →recent activity

Analyzing

Block #87,703,253

26 transactions · 21 stateful · 2026-07-14 12:50:49 UTC

Parallelism

73/100

Blocked

48%

Avg conflicts / tx

1.04

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,703,253  ·  26 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

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0x307414a5…7214

0x34b655…2a6f

8 touches
6 conflicts

0x5170a218…3a84

0xc8689a…ee79

6 touches
3 conflicts

0x7c0bdc54…9dde

0x34b655…2a6f

6 touches
3 conflicts

0x7fa1794c…3323

0x34b655…2a6f

6 touches
3 conflicts

0xb11a3969…fc6a

0x34b655…2a6f

6 touches
3 conflicts

0xdfc21d7c…e062

0x34b655…2a6f

6 touches
3 conflicts

0xe1fe8278…8591

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity