← previous blocknext block →recent activity

Analyzing

Block #93,359,661

25 transactions · 23 stateful · 2026-08-05 13:32:02 UTC

Parallelism

64/100

Blocked

48%

Avg conflicts / tx

1.4

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #93,359,661  ·  25 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

0xab5ba139…ea6f

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0xc5031114…58ac

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x216ffe66…1f94

0x34b655…2a6f

6 touches
3 conflicts

0x75aa78e1…2176

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

10 conflicts on slot 0xab5ba139f3…9fea6f

← previous block·next block →recent activity