← previous blocknext block →recent activity

Analyzing

Block #88,366,393

22 transactions · 20 stateful · 2026-07-17 14:48:05 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.77

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #88,366,393  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x90b56fb4…ae7b

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x427d1120…4eb1

0x34b655…2a6f

6 touches
3 conflicts

0x5b8a1a43…4aea

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

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

10 conflicts on slot 0x90b56fb494…80ae7b

← previous block·next block →recent activity