← previous blocknext block →recent activity

Analyzing

Block #96,541,560

7 transactions · 5 stateful · 2026-08-16 16:48:56 UTC

Parallelism

57/100

Blocked

40%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #96,541,560  ·  7 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

0x0f2d78b1…7363

0x34b655…2a6f

6 touches
3 conflicts

0x097f492f…a7a5

0x34b655…2a6f

4 touches
1 conflict

0x17935a8f…a796

0x34b655…2a6f

4 touches
1 conflict

0x286711a5…b3bf

0x34b655…2a6f

4 touches
1 conflict

0x2e570568…d94d

0x34b655…2a6f

4 touches
1 conflict

0x3a2a8323…3f40

0x34b655…2a6f

4 touches
1 conflict

0x3c7c65d0…0b52

0x34b655…2a6f

4 touches
1 conflict

0x57be321f…fecc

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 0x0f2d78b1bb…5e7363

← previous block·next block →recent activity