← previous blocknext block →recent activity

Analyzing

Block #94,796,276

21 transactions · 21 stateful · 2026-08-10 14:14:16 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,796,276  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xabd0bcfc…64e2

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x1adc270e…f7f6

0x34b655…2a6f

6 touches
3 conflicts

0x5e0b8bbe…377b

0x34b655…2a6f

4 touches
1 conflict

0x62384c7e…edfc

0x34b655…2a6f

4 touches
1 conflict

0x7ec9cda3…6ddb

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 0xabd0bcfc80…a364e2

← previous block·next block →recent activity