← previous blocknext block →recent activity

Analyzing

Block #87,716,498

17 transactions · 15 stateful · 2026-07-14 14:19:38 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

1.12

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,716,498  ·  17 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

8 touches
6 conflicts

0xbf78ee7f…e7fd

0x34b655…2a6f

8 touches
6 conflicts

0x909b34ee…b9e3

0x34b655…2a6f

8 touches
6 conflicts

0xec643e1d…86d8

0xd32edf…ff58

7 touches
6 conflicts

0x4e13b7b0…e55c

0x34b655…2a6f

6 touches
3 conflicts

0x65a7838c…d678

0x34b655…2a6f

6 touches
3 conflicts

0x4a05ec21…e025

0x34b655…2a6f

6 touches
3 conflicts

0x3095aa84…e9e3

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

← previous block·next block →recent activity