← previous blocknext block →recent activity

Analyzing

Block #100,873,561

19 transactions · 17 stateful · 2026-08-31 22:20:12 UTC

Parallelism

84/100

Blocked

29%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,873,561  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x0b3eb43a…ca08

0x34b655…2a6f

4 touches
1 conflict

0x191e0467…70e5

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2f358e74…1022

0x34b655…2a6f

4 touches
1 conflict

0x33b5035a…d1c6

0x34b655…2a6f

4 touches
1 conflict

0x3bfb961d…1dee

0x34b655…2a6f

4 touches
1 conflict

0x4a876a12…694e

0x34b655…2a6f

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 0xaad6be10ae…2c0801

← previous block·next block →recent activity