← previous blocknext block →recent activity

Analyzing

Block #96,016,218

14 transactions · 14 stateful · 2026-08-14 20:46:17 UTC

Parallelism

86/100

Blocked

21%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,016,218  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x784eaad2…d177

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xea154cbb…f280

0x34b655…2a6f

4 touches
1 conflict

0xfbf46d96…882d

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0fb9e50c…1a35

0x34b655…2a6f

4 touches
1 conflict

0x48203298…65cb

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

1 conflict on slot 0x784eaad228…0ad177

← previous block·next block →recent activity