← previous blocknext block →recent activity

Analyzing

Block #96,276,631

21 transactions · 20 stateful · 2026-08-15 18:36:10 UTC

Parallelism

71/100

Blocked

35%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #96,276,631  ·  21 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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x7938c6fd…1cd1

0x34b655…2a6f

6 touches
3 conflicts

0xd0919e62…a2a8

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5e8

0x34b655…2a6f

4 touches
1 conflict

0x06726618…fafd

0x34b655…2a6f

4 touches
1 conflict

0x346f1c15…415a

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity