← previous blocknext block →recent activity

Analyzing

Block #87,133,318

20 transactions · 19 stateful · 2026-07-11 21:18:08 UTC

Parallelism

80/100

Blocked

32%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,133,318  ·  20 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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x06aed19e…ca57

0x34b655…2a6f

4 touches
1 conflict

0x0dd3bdfb…7537

0x34b655…2a6f

4 touches
1 conflict

0x0dd3bdfb…7538

0x34b655…2a6f

4 touches
1 conflict

0x0e9a70ab…e67c

0x34b655…2a6f

4 touches
1 conflict

0x3d4584df…ffed

0x34b655…2a6f

4 touches
1 conflict

0x48e4ba72…3c67

0x34b655…2a6f

4 touches
1 conflict

0x51a0d55f…3622

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity