← previous blocknext block →recent activity

Analyzing

Block #87,661,744

24 transactions · 20 stateful · 2026-07-14 08:13:12 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,661,744  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x745952b2…d90c

0x34b655…2a6f

6 touches
3 conflicts

0xa10e928f…3b92

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x32646adf…e05d

0x34b655…2a6f

4 touches
1 conflict

0x3f7d8a09…362c

0x34b655…2a6f

4 touches
1 conflict

0x560b6fd9…a104

0x34b655…2a6f

4 touches
1 conflict

0x5c79a7db…b7aa

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

6 conflicts on slot 0x0733be30d6…38112f

← previous block·next block →recent activity