← previous blocknext block →recent activity

Analyzing

Block #95,975,700

20 transactions · 19 stateful · 2026-08-14 17:22:23 UTC

Parallelism

55/100

Blocked

53%

Avg conflicts / tx

1.35

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,975,700  ·  20 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

0xbcbf5d09…8bac

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x3adf6cd7…6f2c

0x34b655…2a6f

10 touches
10 conflicts

0xbdc80bf7…e947

0x34b655…2a6f

8 touches
6 conflicts

0x5c2230f4…9294

0x34b655…2a6f

6 touches
3 conflicts

0xafb8e71e…9285

0x34b655…2a6f

6 touches
3 conflicts

0x6f6fc26c…3e34

0x34b655…2a6f

4 touches
1 conflict

0x745a7fd6…5fea

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity