← previous blocknext block →recent activity

Analyzing

Block #87,410,366

21 transactions · 19 stateful · 2026-07-13 04:11:31 UTC

Parallelism

86/100

Blocked

26%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,410,366  ·  21 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

0x6ccf5c86…9954

0x851145…3f07

6 touches
3 conflicts

0xef65bff3…7c9d

0x2a68ba…90c5

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x59a5e379…ad8e

0x34b655…2a6f

4 touches
1 conflict

0x59a5e379…ad8f

0x34b655…2a6f

4 touches
1 conflict

0x69ce640b…884a

0x34b655…2a6f

4 touches
1 conflict

0x7bb84885…1ece

0x34b655…2a6f

4 touches
1 conflict

0x7c01c5d2…8abb

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: 0x851145ea…9f3f07

3 conflicts on slot 0x6ccf5c865d…b29954

← previous block·next block →recent activity