← previous blocknext block →recent activity

Analyzing

Block #96,708,825

18 transactions · 18 stateful · 2026-08-17 06:50:12 UTC

Parallelism

56/100

Blocked

56%

Avg conflicts / tx

1.22

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #96,708,825  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x8cd684d0…c3cb

0x34b655…2a6f

8 touches
6 conflicts

0xc53799eb…d928

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xca09a18f…090f

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0xbe9baf16…df37

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x0672e4a2…8d1f

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 0x8cd684d0d7…f5c3cb

← previous block·next block →recent activity