← previous blocknext block →recent activity

Analyzing

Block #96,593,645

19 transactions · 16 stateful · 2026-08-16 21:10:54 UTC

Parallelism

84/100

Blocked

38%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #96,593,645  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x19b4e3fd…3821

0x34b655…2a6f

6 touches
3 conflicts

0x8c5c7e52…01b8

0x34b655…2a6f

6 touches
3 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0x454cdf57…aebc

0x34b655…2a6f

4 touches
1 conflict

0x4f1e16d4…4833

0x34b655…2a6f

4 touches
1 conflict

0x5bf917f9…f971

0x34b655…2a6f

4 touches
1 conflict

0x5d782da3…0d95

0x34b655…2a6f

4 touches
1 conflict

0x5eac44da…0868

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 0x19b4e3fd69…f93821

← previous block·next block →recent activity