← previous blocknext block →recent activity

Analyzing

Block #94,869,197

12 transactions · 11 stateful · 2026-08-10 20:21:06 UTC

Parallelism

75/100

Blocked

45%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,869,197  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x39fb42f2…35f2

0x34b655…2a6f

4 touches
1 conflict

0x951e757c…8eca

0x34b655…2a6f

4 touches
1 conflict

0x4188cc5f…2d2e

0x34b655…2a6f

4 touches
1 conflict

0x48965dfe…432b

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd80a37f7…9691

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

3 conflicts on slot 0xbde524f475…b143bf

← previous block·next block →recent activity