← previous blocknext block →recent activity

Analyzing

Block #99,265,646

17 transactions · 17 stateful · 2026-08-26 07:09:57 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

1.24

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,265,646  ·  17 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

10 touches
10 conflicts

0xd17580f9…ece1

0x754704…b603

10 touches
10 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x2476b9d0…3967

0x065c9d…c394

2 touches
0 conflicts

0xba38536d…2b7d

0x065c9d…c394

2 touches
0 conflicts

0x1f5a2e2b…65f1

0x2b46c0…1669

2 touches
0 conflicts

0x48ed1159…abe9

0x2b46c0…1669

2 touches
0 conflicts

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

10 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity