← previous blocknext block →recent activity

Analyzing

Block #87,304,489

18 transactions · 16 stateful · 2026-07-12 16:23:24 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,304,489  ·  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

0x9a2de05d…3e6b

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x37ee30c9…9e70

0x34b655…2a6f

4 touches
1 conflict

0x4cdf55e1…0f2d

0x34b655…2a6f

4 touches
1 conflict

0x69473e5b…cb2a

0x34b655…2a6f

4 touches
1 conflict

0x6e3df932…0d53

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0x9a2de05d75…453e6b

← previous block·next block →recent activity