← previous blocknext block →recent activity

Analyzing

Block #96,560,593

18 transactions · 17 stateful · 2026-08-16 18:24:39 UTC

Parallelism

61/100

Blocked

59%

Avg conflicts / tx

1.39

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,560,593  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xbde524f4…43bf

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xff196840…a453

0x34b655…2a6f

6 touches
3 conflicts

0x705ab4ae…0162

0x34b655…2a6f

6 touches
3 conflicts

0xb789c6a4…9bba

0x34b655…2a6f

6 touches
3 conflicts

0x7cd5e47d…59b1

0x34b655…2a6f

5 touches
3 conflicts

0x35a9f06c…7689

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 0xbde524f475…b143bf

← previous block·next block →recent activity