← previous blocknext block →recent activity

Analyzing

Block #87,357,162

19 transactions · 18 stateful · 2026-07-12 22:15:36 UTC

Parallelism

84/100

Blocked

39%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,357,162  ·  19 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

0xe741c135…25a9

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x641aed07…bcb9

0x34b655…2a6f

6 touches
3 conflicts

0xbd9491f7…dd92

0x34b655…2a6f

6 touches
3 conflicts

0x42aad825…b067

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x535b7ebf…ad73

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 0xe741c1358a…4425a9

← previous block·next block →recent activity