← previous blocknext block →recent activity

Analyzing

Block #95,592,007

30 transactions · 22 stateful · 2026-08-13 09:11:06 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.37

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,592,007  ·  30 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x5f7fc558…02ab

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0000

0x659bd0…a9da

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x7e28e55c…d05c

0x754704…b603

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb82

0x1b6862…e19c

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 0x889d5e90c7…59929a

← previous block·next block →recent activity