← previous blocknext block →recent activity

Analyzing

Block #92,525,664

18 transactions · 17 stateful · 2026-08-02 15:34:38 UTC

Parallelism

61/100

Blocked

59%

Avg conflicts / tx

1.39

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,525,664  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0xbdc80bf7…e947

0x34b655…2a6f

8 touches
6 conflicts

0x4333acc5…af14

0x34b655…2a6f

6 touches
6 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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity