← previous blocknext block →recent activity

Analyzing

Block #96,600,996

20 transactions · 20 stateful · 2026-08-16 21:47:53 UTC

Parallelism

75/100

Blocked

35%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,600,996  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x9d34cc12…59a6

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x41f8f5dd…90f5

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x48aded11…c45c

0x34b655…2a6f

4 touches
1 conflict

0x68d3db4e…f6da

0x34b655…2a6f

4 touches
1 conflict

0x74e0d9d2…47d7

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 0x9d34cc12c2…0b59a6

← previous block·next block →recent activity