← previous blocknext block →recent activity

Analyzing

Block #96,209,313

20 transactions · 14 stateful · 2026-08-15 12:57:34 UTC

Parallelism

80/100

Blocked

57%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,209,313  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x3eaa8db8…8ba8

0x34b655…2a6f

8 touches
6 conflicts

0x66bdb4c2…7ea6

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x4e135144…4167

0x34b655…2a6f

4 touches
1 conflict

0x6fb92ed4…7205

0x34b655…2a6f

4 touches
1 conflict

0x72f56d01…046b

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity