← previous blocknext block →recent activity

Analyzing

Block #96,796,430

22 transactions · 20 stateful · 2026-08-17 14:10:49 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.36

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #96,796,430  ·  22 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

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb409e204…89ac

0x34b655…2a6f

6 touches
3 conflicts

0xab1d6786…884e

0x34b655…2a6f

6 touches
3 conflicts

0x966e45cf…0f25

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xbe9baf16…df37

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

← previous block·next block →recent activity