← previous blocknext block →recent activity

Analyzing

Block #87,519,201

25 transactions · 18 stateful · 2026-07-13 16:19:33 UTC

Parallelism

64/100

Blocked

56%

Avg conflicts / tx

0.8

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,519,201  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

10 touches
10 conflicts

0xb5a3b1be…8122

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x589cae60…3ea2

0x40c49f…2af0

4 touches
1 conflict

0x0eeb2a30…6909

0x34b655…2a6f

4 touches
1 conflict

0x689d5e98…d068

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity