← previous blocknext block →recent activity

Analyzing

Block #93,329,242

28 transactions · 25 stateful · 2026-08-05 10:59:05 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

1.21

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #93,329,242  ·  28 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x26c57a37…e45b

0x34b655…2a6f

7 touches
6 conflicts

0x2385516f…eca5

0x34b655…2a6f

6 touches
3 conflicts

0x369a943e…aef6

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

15 conflicts on slot 0xbde524f475…b143bf

← previous block·next block →recent activity