← previous blocknext block →recent activity

Analyzing

Block #95,746,301

18 transactions · 16 stateful · 2026-08-13 22:08:13 UTC

Parallelism

56/100

Blocked

63%

Avg conflicts / tx

1.22

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,746,301  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x6771eae2…7014

0x34b655…2a6f

6 touches
3 conflicts

0x0ae2ec81…0e64

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xee8237bd…46ad

0x34b655…2a6f

6 touches
3 conflicts

0x746bcce3…d0ce

0x34b655…2a6f

4 touches
1 conflict

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity