← previous blocknext block →recent activity

Analyzing

Block #95,382,548

26 transactions · 24 stateful · 2026-08-12 15:36:20 UTC

Parallelism

62/100

Blocked

58%

Avg conflicts / tx

1.42

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #95,382,548  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x3ee7b4dc…d4d0

0x34b655…2a6f

8 touches
6 conflicts

0x143ef3f5…62b1

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xe8eae8a3…bacc

0x34b655…2a6f

8 touches
6 conflicts

0xf6deafb5…5c25

0x34b655…2a6f

8 touches
6 conflicts

0xa9988419…9f45

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity