← previous blocknext block →recent activity

Analyzing

Block #87,420,956

25 transactions · 20 stateful · 2026-07-13 05:22:21 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,420,956  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x305e6edb…89b1

0x34b655…2a6f

6 touches
3 conflicts

0x11d629eb…bcd9

0x34b655…2a6f

6 touches
3 conflicts

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x1fab1722…aec5

0x34b655…2a6f

4 touches
1 conflict

0x2edb240b…5bf6

0x34b655…2a6f

4 touches
1 conflict

0x3d4584df…ffed

0x34b655…2a6f

4 touches
1 conflict

0x67bfbc55…7b2f

0x34b655…2a6f

4 touches
1 conflict

0x6aca3a74…ce9a

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 0x305e6edb9c…d189b1

← previous block·next block →recent activity