← previous blocknext block →recent activity

Analyzing

Block #96,561,634

8 transactions · 7 stateful · 2026-08-16 18:29:53 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #96,561,634  ·  8 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

0xafb8e71e…9285

0x34b655…2a6f

6 touches
3 conflicts

0xfc371f5e…0955

0x34b655…2a6f

4 touches
1 conflict

0xfe5001f7…991f

0x34b655…2a6f

4 touches
1 conflict

0x14eb2f47…8a2e

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x48719cbe…5484

0x34b655…2a6f

4 touches
1 conflict

0x4f858307…7642

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…aaff

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 0xafb8e71eb0…ec9285

← previous block·next block →recent activity