← previous blocknext block →recent activity

Analyzing

Block #100,584,386

16 transactions · 15 stateful · 2026-08-30 22:05:08 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,584,386  ·  16 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

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd814f518…f5b4

0x34b655…2a6f

4 touches
1 conflict

0xe7ad475a…0e41

0x34b655…2a6f

4 touches
1 conflict

0x5f0a01c3…8269

0x851145…3f07

4 touches
1 conflict

0x87d39100…7270

0x851145…3f07

4 touches
1 conflict

0xf2f76ab3…623e

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

← previous block·next block →recent activity