← previous blocknext block →recent activity

Analyzing

Block #87,064,054

11 transactions · 9 stateful · 2026-07-11 13:35:34 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.36

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #87,064,054  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf324b405…ca30

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x008accc4…1da7

0x34b655…2a6f

4 touches
1 conflict

0x008accc4…1da8

0x34b655…2a6f

4 touches
1 conflict

0x0aa5b76b…60db

0x34b655…2a6f

4 touches
1 conflict

0x0f2efde2…67da

0x34b655…2a6f

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

1 conflict on slot 0xf324b40549…56ca30

← previous block·next block →recent activity