← previous blocknext block →recent activity

Analyzing

Block #94,663,576

20 transactions · 18 stateful · 2026-08-10 03:05:19 UTC

Parallelism

35/100

Blocked

67%

Avg conflicts / tx

2

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #94,663,576  ·  20 txs across 13 waves  ·  depth 13
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

wave w12

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

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0x4f1ad4b4…e00a

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x9b8d95b1…1a50

0x34b655…2a6f

6 touches
3 conflicts

0x53699236…fede

0x34b655…2a6f

6 touches
3 conflicts

0x41377979…0a18

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

10 conflicts on slot 0x737acb7813…fafce8

← previous block·next block →recent activity