← previous blocknext block →recent activity

Analyzing

Block #93,076,001

23 transactions · 20 stateful · 2026-08-04 13:45:00 UTC

Parallelism

57/100

Blocked

55%

Avg conflicts / tx

1.61

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #93,076,001  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

14 touches
21 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x033cf007…136d

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x7df11bd9…ae75

0x34b655…2a6f

7 touches
6 conflicts

0xca841faa…486a

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

21 conflicts on slot 0xbde524f475…b143bf

← previous block·next block →recent activity