← previous blocknext block →recent activity

Analyzing

Block #96,599,648

16 transactions · 15 stateful · 2026-08-16 21:41:06 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,599,648  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x69411fb3…e36d

0x34b655…2a6f

8 touches
6 conflicts

0x2d651956…12e8

0x34b655…2a6f

8 touches
6 conflicts

0xa6176fff…d2c5

0x34b655…2a6f

6 touches
3 conflicts

0x42041fec…bd86

0x754704…b603

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x69c844bd…c9de

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x97c823ec…9944

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

6 conflicts on slot 0x69411fb3ba…bce36d

← previous block·next block →recent activity