← previous blocknext block →recent activity

Analyzing

Block #87,355,684

23 transactions · 21 stateful · 2026-07-12 22:05:44 UTC

Parallelism

57/100

Blocked

62%

Avg conflicts / tx

1.61

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,355,684  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xfaef08b1…0696

0x34b655…2a6f

14 touches
21 conflicts

0x8388eab6…83ff

0x34b655…2a6f

14 touches
21 conflicts

0xba559de1…6d2c

0x34b655…2a6f

12 touches
15 conflicts

0x9e9c4e1e…4f14

0x34b655…2a6f

12 touches
15 conflicts

0x727fbce7…0c80

0x34b655…2a6f

12 touches
15 conflicts

0x7506443a…4820

0x34b655…2a6f

12 touches
15 conflicts

0xd50cd2ef…8474

0x34b655…2a6f

12 touches
15 conflicts

0x63c900f4…2600

0x34b655…2a6f

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 0xfaef08b108…f90696

← previous block·next block →recent activity