← previous blocknext block →recent activity

Analyzing

Block #92,554,505

17 transactions · 16 stateful · 2026-08-02 17:59:40 UTC

Parallelism

53/100

Blocked

69%

Avg conflicts / tx

1.24

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #92,554,505  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x34f17697…e85a

0x34b655…2a6f

6 touches
3 conflicts

0xf5aef04f…989e

0x34b655…2a6f

6 touches
3 conflicts

0x6b2ba712…0214

0x34b655…2a6f

6 touches
3 conflicts

0x9d72189f…0cb0

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

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 0xca841faae5…71486a

← previous block·next block →recent activity