← previous blocknext block →recent activity

Analyzing

Block #95,000,593

20 transactions · 18 stateful · 2026-08-11 07:21:56 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,000,593  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00966e54…7d1d

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x0d488000…3831

0x34b655…2a6f

6 touches
3 conflicts

0x589623ea…8ce2

0x34b655…2a6f

6 touches
3 conflicts

0x6eb3e5af…064e

0x34b655…2a6f

6 touches
3 conflicts

0x86977b3d…a9c4

0x34b655…2a6f

6 touches
3 conflicts

0xd81dbbb9…d0c5

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity