← previous blocknext block →recent activity

Analyzing

Block #87,295,043

18 transactions · 17 stateful · 2026-07-12 15:20:18 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.17

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,295,043  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x321eac33…6aca

0x34b655…2a6f

8 touches
6 conflicts

0x4abfb389…18f4

0x34b655…2a6f

6 touches
3 conflicts

0x5e02109f…c11b

0x34b655…2a6f

6 touches
3 conflicts

0x636fd21a…9978

0x34b655…2a6f

6 touches
3 conflicts

0x067c61b8…650f

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

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

6 conflicts on slot 0x92385428ad…dc6941

← previous block·next block →recent activity