← previous blocknext block →recent activity

Analyzing

Block #96,218,337

6 transactions · 6 stateful · 2026-08-15 13:42:58 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,218,337  ·  6 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x0fe1e6e0…f553

0x34b655…2a6f

4 touches
1 conflict

0x53f393fa…00b9

0x34b655…2a6f

4 touches
1 conflict

0x61e273d4…7a19

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x74e0d9d2…47d7

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xdf6c3e51…c493

0x34b655…2a6f

4 touches
1 conflict

0x2f4b1dc8…e9fa

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x0fe1e6e0ec…9df553

← previous block·next block →recent activity