← previous blocknext block →recent activity

Analyzing

Block #95,247,775

31 transactions · 25 stateful · 2026-08-12 04:13:58 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

1.13

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,247,775  ·  31 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x22e0cc1d…ad0d

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xb2195a0c…68ca

0x34b655…2a6f

8 touches
6 conflicts

0x57be321f…fecc

0x34b655…2a6f

8 touches
6 conflicts

0xd9461b7e…31bc

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity