← previous blocknext block →recent activity

Analyzing

Block #95,124,776

23 transactions · 22 stateful · 2026-08-11 17:47:27 UTC

Parallelism

61/100

Blocked

45%

Avg conflicts / tx

1.39

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,124,776  ·  23 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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x3a5581fb…e85c

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc5a1b2fe…5369

0x34b655…2a6f

6 touches
3 conflicts

0xa56e54d0…2d39

0x34b655…2a6f

4 touches
1 conflict

0xacd1b162…bee6

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity