← previous blocknext block →recent activity

Analyzing

Block #95,915,523

18 transactions · 17 stateful · 2026-08-14 12:19:38 UTC

Parallelism

56/100

Blocked

53%

Avg conflicts / tx

1.83

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,915,523  ·  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

0x4acbdbcf…a8c6

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xb255781f…2ffb

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x8b98eea2…60b0

0x34b655…2a6f

6 touches
3 conflicts

0x9a36cb2e…0929

0x34b655…2a6f

6 touches
3 conflicts

0x0a7a49dc…a295

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

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

21 conflicts on slot 0x4acbdbcf7f…d0a8c6

← previous block·next block →recent activity