← previous blocknext block →recent activity

Analyzing

Block #93,231,000

18 transactions · 16 stateful · 2026-08-05 02:45:08 UTC

Parallelism

67/100

Blocked

56%

Avg conflicts / tx

1.22

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,231,000  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xf1cc9519…84c1

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xfed09e59…a493

0x34b655…2a6f

6 touches
3 conflicts

0x41f1e2e5…2edf

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd8341551…6261

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

← previous block·next block →recent activity