← previous blocknext block →recent activity

Analyzing

Block #87,579,033

21 transactions · 19 stateful · 2026-07-13 23:00:16 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,579,033  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xb988c952…a33e

0x34b655…2a6f

6 touches
3 conflicts

0xe06bbb2e…9416

0x34b655…2a6f

6 touches
3 conflicts

0xe06bbb2e…9417

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

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

3 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity