← previous blocknext block →recent activity

Analyzing

Block #86,957,014

20 transactions · 17 stateful · 2026-07-11 01:40:23 UTC

Parallelism

85/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,957,014  ·  20 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

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x1941b441…5889

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09d

0x34b655…2a6f

4 touches
1 conflict

0x33bd5ec4…af53

0xa6afd3…d132

4 touches
1 conflict

0x2b7950c1…2342

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 0x92385428ad…dc6941

← previous block·next block →recent activity