← previous blocknext block →recent activity

Analyzing

Block #94,848,804

24 transactions · 23 stateful · 2026-08-10 18:38:32 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

1.17

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #94,848,804  ·  24 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

0xa558e115…fc88

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

6 touches
3 conflicts

0x90d66298…42f2

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x4cabb80a…46bf

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

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 0xa558e11562…cafc88

← previous block·next block →recent activity