← previous blocknext block →recent activity

Analyzing

Block #95,522,441

24 transactions · 23 stateful · 2026-08-13 03:21:13 UTC

Parallelism

71/100

Blocked

30%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,522,441  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc5a1b2fe…5369

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00ddbbf2…4588

0x34b655…2a6f

6 touches
3 conflicts

0x7b67f6cf…0aab

0x34b655…2a6f

4 touches
1 conflict

0x7c37629d…9e3f

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

6 conflicts on slot 0xc5a1b2febf…f05369

← previous block·next block →recent activity