← previous blocknext block →recent activity

Analyzing

Block #96,299,864

24 transactions · 22 stateful · 2026-08-15 20:33:01 UTC

Parallelism

79/100

Blocked

32%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,299,864  ·  24 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

0x53f393fa…00b9

0x34b655…2a6f

10 touches
10 conflicts

0xdec6a8f8…be18

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x3f0a88e0…392e

0x34b655…2a6f

4 touches
1 conflict

0x48b8d2e5…3f2f

0x34b655…2a6f

4 touches
1 conflict

0x5af10b50…8d5c

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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

10 conflicts on slot 0x53f393fafd…2a00b9

← previous block·next block →recent activity