← previous blocknext block →recent activity

Analyzing

Block #86,625,223

21 transactions · 19 stateful · 2026-07-09 12:42:10 UTC

Parallelism

57/100

Blocked

53%

Avg conflicts / tx

1.33

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,625,223  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd99b3b64…1c95

0x34b655…2a6f

12 touches
15 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0xba559de1…6d2c

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x7523ad90…2ba5

0x34b655…2a6f

6 touches
3 conflicts

0x9ad66bbf…929c

0x34b655…2a6f

6 touches
3 conflicts

0xa8f3c19e…b6f6

0x34b655…2a6f

6 touches
3 conflicts

0xb0bc3bf8…e2b1

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

15 conflicts on slot 0xd99b3b6441…7a1c95

← previous block·next block →recent activity