← previous blocknext block →recent activity

Analyzing

Block #86,979,140

19 transactions · 19 stateful · 2026-07-11 04:08:12 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,979,140  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x1941b441…5889

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x2356194c…0d6b

0x34b655…2a6f

6 touches
3 conflicts

0x33bd5ec4…af53

0xa6afd3…d132

4 touches
1 conflict

0x45c033be…0aad

0x34b655…2a6f

4 touches
1 conflict

0x4e3abeff…18eb

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity