← previous blocknext block →recent activity

Analyzing

Block #95,645,471

24 transactions · 19 stateful · 2026-08-13 13:40:02 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

1.42

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,645,471  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf3d10975…0d07

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0x00ddbbf2…4588

0x34b655…2a6f

8 touches
6 conflicts

0x66d5e476…8a1f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xfa2527aa…9dd5

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 0xf3d10975b0…050d07

← previous block·next block →recent activity