← previous blocknext block →recent activity

Analyzing

Block #95,536,007

19 transactions · 16 stateful · 2026-08-13 04:29:27 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,536,007  ·  19 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

0x2a9e9bd1…5368

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x11b69a7e…334e

0xee8c0e…1242

6 touches
3 conflicts

0xc99dd704…cf7d

0xa6afd3…d132

5 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c0

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

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

3 conflicts on slot 0x2a9e9bd1e2…355368

← previous block·next block →recent activity