← previous blocknext block →recent activity

Analyzing

Block #87,418,747

18 transactions · 17 stateful · 2026-07-13 05:07:35 UTC

Parallelism

83/100

Blocked

41%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,418,747  ·  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

0x5f57e7ab…9f8d

0x34b655…2a6f

6 touches
3 conflicts

0xc08384da…ecb7

0x34b655…2a6f

6 touches
3 conflicts

0x2b5101ac…090b

0x34b655…2a6f

6 touches
3 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0x4aa2bfeb…ca33

0x34b655…2a6f

4 touches
1 conflict

0x67db761a…4fa1

0x34b655…2a6f

4 touches
1 conflict

0x8a5e719f…6328

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

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 0x5f57e7ab19…059f8d

← previous block·next block →recent activity