← previous blocknext block →recent activity

Analyzing

Block #87,590,077

21 transactions · 20 stateful · 2026-07-14 00:14:07 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.29

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,590,077  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x03fb27fd…0c06

0x34b655…2a6f

14 touches
21 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

14 touches
21 conflicts

0x2c2a7f3c…015f

0x34b655…2a6f

14 touches
21 conflicts

0x39c4bc47…ce30

0x34b655…2a6f

14 touches
21 conflicts

0x3a876cd9…2450

0x34b655…2a6f

14 touches
21 conflicts

0x63c900f4…2600

0x34b655…2a6f

14 touches
21 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x864353d4…dcb7

0x34b655…2a6f

14 touches
21 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

21 conflicts on slot 0x03fb27fddd…f00c06

← previous block·next block →recent activity