← previous blocknext block →recent activity

Analyzing

Block #95,555,911

28 transactions · 24 stateful · 2026-08-13 06:09:33 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.36

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,555,911  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x16ca898b…f2b0

0x34b655…2a6f

4 touches
1 conflict

0x1a5d321d…a474

0x34b655…2a6f

4 touches
1 conflict

0x3b9bb58c…e73a

0x34b655…2a6f

4 touches
1 conflict

0x43fd3667…094b

0x34b655…2a6f

4 touches
1 conflict

0x66d5e476…8a1f

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 0xb3fb9fb561…7664db

← previous block·next block →recent activity