← previous blocknext block →recent activity

Analyzing

Block #93,553,172

21 transactions · 18 stateful · 2026-08-06 05:44:52 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,553,172  ·  21 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

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x2a72c9ad…5bdc

0x34b655…2a6f

4 touches
1 conflict

0x69a45f39…39aa

0x34b655…2a6f

4 touches
1 conflict

0x850def09…120b

0x34b655…2a6f

4 touches
1 conflict

0xa13e2069…6171

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

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 0x002fed350f…7379fa

← previous block·next block →recent activity