← previous blocknext block →recent activity

Analyzing

Block #96,435,915

11 transactions · 7 stateful · 2026-08-16 07:57:15 UTC

Parallelism

73/100

Blocked

57%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #96,435,915  ·  11 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

0x9e6be63e…d886

0x34b655…2a6f

6 touches
3 conflicts

0x53f393fa…00b9

0x34b655…2a6f

4 touches
1 conflict

0xbeedaa05…9eda

0x34b655…2a6f

4 touches
1 conflict

0xc1f6acda…6abb

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xdc3d4f40…12c9

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xfe39a1f7…8eb0

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 0x9e6be63ef2…84d886

← previous block·next block →recent activity