← previous blocknext block →recent activity

Analyzing

Block #93,456,267

22 transactions · 20 stateful · 2026-08-05 21:37:44 UTC

Parallelism

64/100

Blocked

45%

Avg conflicts / tx

1.05

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,456,267  ·  22 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

0xbde524f4…43bf

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x01ec2e0a…d1ac

0x34b655…2a6f

8 touches
6 conflicts

0xa1bdd5c6…fbd1

0x34b655…2a6f

6 touches
3 conflicts

0x428b6e5b…8909

0x34b655…2a6f

6 touches
3 conflicts

0x4e8c4408…d37a

0x34b655…2a6f

6 touches
3 conflicts

0x4e8c4408…d37b

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 0xbde524f475…b143bf

← previous block·next block →recent activity