← previous blocknext block →recent activity

Analyzing

Block #87,284,612

18 transactions · 15 stateful · 2026-07-12 14:10:32 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,284,612  ·  18 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

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x38bdc5d3…a632

0x34b655…2a6f

4 touches
1 conflict

0x5d7f309d…5145

0x34b655…2a6f

4 touches
1 conflict

0x5ed0df97…66ed

0x34b655…2a6f

4 touches
1 conflict

0x6cedc82d…847a

0x34b655…2a6f

4 touches
1 conflict

0x74888025…a5b8

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xa0b17484…2b19

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity