← previous blocknext block →recent activity

Analyzing

Block #87,410,403

19 transactions · 18 stateful · 2026-07-13 04:11:48 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,410,403  ·  19 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

0x086db8fc…0024

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x801058a8…5bc3

0x34b655…2a6f

6 touches
3 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

4 touches
1 conflict

0x427f51fd…bd80

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

0x34b655…2a6f

4 touches
1 conflict

0x63e417f8…2e72

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

10 conflicts on slot 0x086db8fc6e…830024

← previous block·next block →recent activity