← previous blocknext block →recent activity

Analyzing

Block #87,579,031

18 transactions · 18 stateful · 2026-07-13 23:00:15 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,579,031  ·  18 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

0xb988c952…a33e

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x830b63a6…8105

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x503b3a72…f6df

0x34b655…2a6f

4 touches
1 conflict

0x640b61a9…cda9

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 0xb988c9529a…bba33e

← previous block·next block →recent activity