← previous blocknext block →recent activity

Analyzing

Block #96,825,104

8 transactions · 6 stateful · 2026-08-17 16:35:03 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #96,825,104  ·  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

0x5bd4991d…1c41

0x34b655…2a6f

4 touches
1 conflict

0x4f858307…7642

0x34b655…2a6f

4 touches
1 conflict

0x92132ed7…2722

0x34b655…2a6f

4 touches
1 conflict

0x9e599b87…c270

0x34b655…2a6f

4 touches
1 conflict

0xdd88af49…a3b7

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x216ffe66…1f94

0x34b655…2a6f

2 touches
0 conflicts

0x4039f67f…d742

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 0x5bd4991d8b…341c41

← previous block·next block →recent activity