← previous blocknext block →recent activity

Analyzing

Block #93,362,393

24 transactions · 24 stateful · 2026-08-05 13:45:46 UTC

Parallelism

50/100

Blocked

63%

Avg conflicts / tx

2.33

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #93,362,393  ·  24 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x737acb78…fce8

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xcc3207c1…fad6

0x34b655…2a6f

8 touches
6 conflicts

0x2385516f…eca5

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xb832ec52…48e8

0x34b655…2a6f

7 touches
6 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