← previous blocknext block →recent activity

Analyzing

Block #99,134,184

21 transactions · 19 stateful · 2026-08-25 20:08:28 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,134,184  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xb6ebe2b7…135c

0x065c9d…c394

7 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0003

0x094452…0a09

4 touches
1 conflict

0x00000000…0004

0x094452…0a09

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf9da5665…2703

0x754704…b603

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

15 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity