← previous blocknext block →recent activity

Analyzing

Block #95,085,848

27 transactions · 23 stateful · 2026-08-11 14:31:37 UTC

Parallelism

63/100

Blocked

57%

Avg conflicts / tx

1.59

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #95,085,848  ·  27 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x99701186…1cbf

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0d2de0f6…e6c6

0x34b655…2a6f

8 touches
6 conflicts

0xdfc2c1fb…6dc6

0x34b655…2a6f

8 touches
6 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

6 touches
3 conflicts

0x93ef53c7…f210

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

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 0xca841faae5…71486a

← previous block·next block →recent activity