← previous blocknext block →recent activity

Analyzing

Block #100,562,620

31 transactions · 29 stateful · 2026-08-30 20:15:39 UTC

Parallelism

87/100

Blocked

24%

Avg conflicts / tx

0.26

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,562,620  ·  31 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

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xd6bd849a…5597

0x2a68ba…90c5

4 touches
1 conflict

0x10abefc9…c9bc

0x2b46c0…1669

4 touches
1 conflict

0x10d80fee…dbda

0x2b46c0…1669

4 touches
1 conflict

0x2f4b2cf9…4e1e

0x2b46c0…1669

4 touches
1 conflict

0x595839b9…ca61

0x2b46c0…1669

4 touches
1 conflict

0x5cc231f5…f1cd

0x2b46c0…1669

4 touches
1 conflict

0x7aa91b8f…d070

0x2b46c0…1669

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

← previous block·next block →recent activity