← previous blocknext block →recent activity

Analyzing

Block #87,715,994

19 transactions · 17 stateful · 2026-07-14 14:16:13 UTC

Parallelism

74/100

Blocked

35%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,715,994  ·  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

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641d

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641e

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x8b818135…eff8

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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

3 conflicts on slot 0x8bf661cb38…d4bcd2

← previous block·next block →recent activity