← previous blocknext block →recent activity

Analyzing

Block #96,278,003

8 transactions · 6 stateful · 2026-08-15 18:43:04 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,278,003  ·  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

0x49ffd065…33d1

0x34b655…2a6f

6 touches
3 conflicts

0x1b1d960e…13de

0x34b655…2a6f

4 touches
1 conflict

0x60f63d67…5ba0

0x34b655…2a6f

4 touches
1 conflict

0x81561f70…fefd

0x34b655…2a6f

4 touches
1 conflict

0xa4e9800f…4ab0

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x0505bae8…b4fb

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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 0x49ffd065b3…cd33d1

← previous block·next block →recent activity