← previous blocknext block →recent activity

Analyzing

Block #88,158,454

20 transactions · 19 stateful · 2026-07-16 15:36:02 UTC

Parallelism

50/100

Blocked

63%

Avg conflicts / tx

1.6

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #88,158,454  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x923c57f1…7810

0x34b655…2a6f

8 touches
6 conflicts

0x35eed8dc…c0c3

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xf3fbc9b8…ab58

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x2c5257fd…4168

0x34b655…2a6f

6 touches
3 conflicts

0x587911c7…9e01

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity