← previous blocknext block →recent activity

Analyzing

Block #87,355,054

25 transactions · 24 stateful · 2026-07-12 22:01:31 UTC

Parallelism

68/100

Blocked

38%

Avg conflicts / tx

1.08

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,355,054  ·  25 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

0x22e0cc1d…ad0d

0x34b655…2a6f

14 touches
21 conflicts

0x321eac33…6aca

0x34b655…2a6f

12 touches
15 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

12 touches
15 conflicts

0x55c1a07a…51ea

0x34b655…2a6f

12 touches
15 conflicts

0x63c900f4…2600

0x34b655…2a6f

12 touches
15 conflicts

0x727fbce7…0c80

0x34b655…2a6f

12 touches
15 conflicts

0x7506443a…4820

0x34b655…2a6f

12 touches
15 conflicts

0x922c7ebd…6600

0xc8689a…ee79

12 touches
15 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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity