← previous blocknext block →recent activity

Analyzing

Block #95,714,412

21 transactions · 18 stateful · 2026-08-13 19:27:46 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,714,412  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xf90c6521…d8f0

0x34b655…2a6f

6 touches
3 conflicts

0xa7d36805…6bb8

0x34b655…2a6f

6 touches
3 conflicts

0x5e2ea201…12de

0x34b655…2a6f

6 touches
3 conflicts

0x620b761c…270e

0x34b655…2a6f

6 touches
3 conflicts

0x4bfdcd51…9b58

0x34b655…2a6f

4 touches
1 conflict

0x4e58deff…c5d0

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 0x482471adbb…39122f

← previous block·next block →recent activity