← previous blocknext block →recent activity

Analyzing

Block #95,201,130

21 transactions · 20 stateful · 2026-08-12 00:11:29 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

1.24

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,201,130  ·  21 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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x550e12cc…8985

0x34b655…2a6f

8 touches
6 conflicts

0x524f0872…0d12

0x34b655…2a6f

8 touches
6 conflicts

0xacd1b162…bee6

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

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 0xca841faae5…71486a

← previous block·next block →recent activity