← previous blocknext block →recent activity

Analyzing

Block #95,181,346

8 transactions · 6 stateful · 2026-08-11 22:31:59 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,181,346  ·  8 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x93ce58d1…a6fa

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x3f4f9f22…8ad6

0x34b655…2a6f

4 touches
1 conflict

0x04d86e8c…16a3

0x34b655…2a6f

4 touches
1 conflict

0x3b6e959d…158f

0x34b655…2a6f

4 touches
1 conflict

0xa779293b…5e59

0x34b655…2a6f

4 touches
1 conflict

0x5060cdde…445d

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 0x482471adbb…39122f

← previous block·next block →recent activity