← previous blocknext block →recent activity

Analyzing

Block #96,264,535

17 transactions · 16 stateful · 2026-08-15 17:35:20 UTC

Parallelism

88/100

Blocked

25%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,264,535  ·  17 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

0x28f3c4a3…6d6c

0x34b655…2a6f

4 touches
1 conflict

0x575f6146…c232

0x34b655…2a6f

4 touches
1 conflict

0x66bdb4c2…7ea6

0x34b655…2a6f

4 touches
1 conflict

0xa6848351…2238

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd0919e62…a2a8

0x34b655…2a6f

4 touches
1 conflict

0xf28d07b9…4fb2

0x34b655…2a6f

4 touches
1 conflict

0xf40e9839…0001

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

1 conflict on slot 0x28f3c4a394…106d6c

← previous block·next block →recent activity