← previous blocknext block →recent activity

Analyzing

Block #87,611,085

24 transactions · 21 stateful · 2026-07-14 02:34:37 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,611,085  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xf2f40f08…5cdb

0x34b655…2a6f

6 touches
3 conflicts

0x745952b2…d90c

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x5b6a7552…a4b8

0x34b655…2a6f

4 touches
1 conflict

0x5b6a7552…a4b9

0x34b655…2a6f

4 touches
1 conflict

0x69ce640b…884a

0x34b655…2a6f

4 touches
1 conflict

0x9c73dcaf…13c2

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

6 conflicts on slot 0x92385428ad…dc6941

← previous block·next block →recent activity