← previous blocknext block →recent activity

Analyzing

Block #95,008,184

21 transactions · 21 stateful · 2026-08-11 08:00:09 UTC

Parallelism

62/100

Blocked

57%

Avg conflicts / tx

1.62

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,008,184  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xcda18b0b…6a4c

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0xbf7ce7a7…1d9e

0x34b655…2a6f

10 touches
10 conflicts

0xbf7817bc…52f6

0x34b655…2a6f

9 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xcb21158b…f18d

0x34b655…2a6f

8 touches
6 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 0xcda18b0bef…046a4c

← previous block·next block →recent activity