← previous blocknext block →recent activity

Analyzing

Block #95,245,035

29 transactions · 26 stateful · 2026-08-12 03:53:37 UTC

Parallelism

76/100

Blocked

35%

Avg conflicts / tx

0.97

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,245,035  ·  29 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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

12 touches
15 conflicts

0xce54c462…7f74

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x00ddbbf2…4588

0x34b655…2a6f

6 touches
3 conflicts

0x10536e59…b234

0x34b655…2a6f

6 touches
3 conflicts

0x1526b11f…8b21

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 0xc824469a90…af6425

← previous block·next block →recent activity