← previous blocknext block →recent activity

Analyzing

Block #87,315,754

20 transactions · 19 stateful · 2026-07-12 17:38:44 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

1.05

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,315,754  ·  20 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

10 touches
10 conflicts

0xc36fa358…24cb

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…000b

0x90c374…be45

10 touches
10 conflicts

0x00000000…000a

0x90c374…be45

10 touches
10 conflicts

0x10a2bd5d…ad6d

0x8d1565…6723

10 touches
10 conflicts

0xa09be165…16b9

0x34b655…2a6f

8 touches
6 conflicts

0xd3a5c8e3…51f3

0x34b655…2a6f

6 touches
3 conflicts

0x47d4745e…02bb

0x336ed4…c59c

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

10 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity