← previous blocknext block →recent activity

Analyzing

Block #96,702,037

13 transactions · 11 stateful · 2026-08-17 06:16:03 UTC

Parallelism

69/100

Blocked

45%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,702,037  ·  13 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

0xa6b89ebb…a66e

0x34b655…2a6f

6 touches
3 conflicts

0x22e2efd1…ae3d

0x34b655…2a6f

4 touches
1 conflict

0x45911da6…5523

0x34b655…2a6f

4 touches
1 conflict

0x4a5956ef…e226

0x34b655…2a6f

4 touches
1 conflict

0x5e0b8bbe…377b

0x34b655…2a6f

4 touches
1 conflict

0x672e6cef…f783

0x34b655…2a6f

4 touches
1 conflict

0x74462c1e…84f3

0x34b655…2a6f

4 touches
1 conflict

0x84d74093…7808

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 0xa6b89ebbaf…5fa66e

← previous block·next block →recent activity