← previous blocknext block →recent activity

Analyzing

Block #95,369,952

21 transactions · 19 stateful · 2026-08-12 14:32:31 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,369,952  ·  21 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

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0x120847e2…98c2

0x34b655…2a6f

4 touches
1 conflict

0x48965dfe…432b

0x34b655…2a6f

4 touches
1 conflict

0x4f97aa17…6776

0x34b655…2a6f

4 touches
1 conflict

0x5a19ef35…dc70

0x34b655…2a6f

4 touches
1 conflict

0x7e3cc3e1…ced8

0x34b655…2a6f

4 touches
1 conflict

0x8046ca3c…f094

0x34b655…2a6f

4 touches
1 conflict

0xa45116ed…5331

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: Kuru Exchange: MarginAccount

1 conflict on slot 0x1125877469…519892

← previous block·next block →recent activity