← previous blocknext block →recent activity

Analyzing

Block #95,577,567

27 transactions · 26 stateful · 2026-08-13 07:58:28 UTC

Parallelism

74/100

Blocked

35%

Avg conflicts / tx

0.59

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,577,567  ·  27 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

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x5767fdec…d9d4

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x458b9085…9ee2

0x34b655…2a6f

4 touches
1 conflict

0x60abda94…c52d

0x34b655…2a6f

4 touches
1 conflict

0x706c758c…2fdb

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

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

10 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity