← previous blocknext block →recent activity

Analyzing

Block #87,724,677

20 transactions · 19 stateful · 2026-07-14 15:14:22 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,724,677  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf5ea108a…dbf6

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x64a058c6…74a1

0x34b655…2a6f

6 touches
3 conflicts

0xa2ea76a0…a726

0x34b655…2a6f

6 touches
3 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x30e49b8b…5fe9

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

6 conflicts on slot 0xf5ea108a6a…e5dbf6

← previous block·next block →recent activity