← previous blocknext block →recent activity

Analyzing

Block #93,468,728

22 transactions · 22 stateful · 2026-08-05 22:40:23 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,468,728  ·  22 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

0x52b477bc…7ccf

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x428b6e5b…8909

0x34b655…2a6f

4 touches
1 conflict

0x434a99da…6442

0x34b655…2a6f

4 touches
1 conflict

0x4e8c4408…d37a

0x34b655…2a6f

4 touches
1 conflict

0x4e8c4408…d37b

0x34b655…2a6f

4 touches
1 conflict

0x5e0b8bbe…377b

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x52b477bcb8…5d7ccf

← previous block·next block →recent activity