← previous blocknext block →recent activity

Analyzing

Block #88,184,600

21 transactions · 19 stateful · 2026-07-16 18:31:24 UTC

Parallelism

48/100

Blocked

58%

Avg conflicts / tx

1.71

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #88,184,600  ·  21 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x326a02b5…8dad

0x34b655…2a6f

12 touches
15 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x517d8281…14d1

0x34b655…2a6f

6 touches
3 conflicts

0xfb53ecf8…bd11

0x34b655…2a6f

6 touches
3 conflicts

0x120847e2…98c2

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x98cc6884…3a83

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 0x326a02b5c5…5c8dad

← previous block·next block →recent activity