← previous blocknext block →recent activity

Analyzing

Block #93,358,226

19 transactions · 19 stateful · 2026-08-05 13:24:49 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,358,226  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x74362807…e577

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0x45ea7a97…bbb3

0x34b655…2a6f

6 touches
3 conflicts

0x803eb45d…00bd

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

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

6 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity