← previous blocknext block →recent activity

Analyzing

Block #96,016,904

24 transactions · 20 stateful · 2026-08-14 20:49:45 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #96,016,904  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x31616f97…1acc

0x34b655…2a6f

6 touches
3 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

6 touches
3 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x50a054d8…9506

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xf219f7cf…7379

0xa6afd3…d132

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 0x31616f9701…df1acc

← previous block·next block →recent activity