← previous blocknext block →recent activity

Analyzing

Block #96,637,279

19 transactions · 18 stateful · 2026-08-17 00:50:22 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,637,279  ·  19 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

0x6bdb9869…7558

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xe999cbf5…d18a

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6c444777…6c84

0x34b655…2a6f

4 touches
1 conflict

0x8252706a…7ca5

0x34b655…2a6f

4 touches
1 conflict

0xc092f0d5…9d89

0x34b655…2a6f

4 touches
1 conflict

0xc7277122…8339

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 0x6bdb9869c7…427558

← previous block·next block →recent activity