← previous blocknext block →recent activity

Analyzing

Block #87,750,504

23 transactions · 21 stateful · 2026-07-14 18:07:09 UTC

Parallelism

65/100

Blocked

62%

Avg conflicts / tx

1.61

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,750,504  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x6ca32a09…4e48

0x34b655…2a6f

14 touches
21 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x06040b44…e244

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xfabd5e92…bfec

0x34b655…2a6f

8 touches
6 conflicts

0x5170a218…3a84

0xc8689a…ee79

6 touches
3 conflicts

0x1435fd06…60ea

0x34b655…2a6f

6 touches
3 conflicts

0x3a2a8323…3f40

0x34b655…2a6f

6 touches
3 conflicts

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

21 conflicts on slot 0x6ca32a096a…2c4e48

← previous block·next block →recent activity