← previous blocknext block →recent activity

Analyzing

Block #95,985,803

14 transactions · 11 stateful · 2026-08-14 18:13:12 UTC

Parallelism

79/100

Blocked

18%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,985,803  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xd6d040d9…9ae3

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x35a9f06c…7689

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x7b55198a…b946

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eeb

0x34b655…2a6f

4 touches
1 conflict

0xa6464996…3af9

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

3 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity