← previous blocknext block →recent activity

Analyzing

Block #87,420,782

24 transactions · 20 stateful · 2026-07-13 05:21:11 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.79

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,420,782  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ac

0xb1dbf0…c0d3

8 touches
6 conflicts

0x8a35acfb…d1ad

0xb1dbf0…c0d3

7 touches
6 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

6 touches
3 conflicts

0x2099241a…2d2a

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

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 0x482471adbb…39122f

← previous block·next block →recent activity