← previous blocknext block →recent activity

Analyzing

Block #96,075,509

16 transactions · 14 stateful · 2026-08-15 01:44:33 UTC

Parallelism

69/100

Blocked

57%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,075,509  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x425376d1…8979

0x34b655…2a6f

6 touches
3 conflicts

0xd93edb3f…94ec

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x42e917f7…ed8c

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xbf3cbeb8…99f0

0x34b655…2a6f

4 touches
1 conflict

0xd732bc76…2844

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 0x425376d1f8…8e8979

← previous block·next block →recent activity