← previous blocknext block →recent activity

Analyzing

Block #106,273,009

29 transactions · 25 stateful · 2026-09-19 20:31:07 UTC

Parallelism

90/100

Blocked

20%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #106,273,009  ·  29 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

0x5c7b5ec0…0764

0x34b655…2a6f

4 touches
1 conflict

0x8dd36ab5…9da1

0x34b655…2a6f

4 touches
1 conflict

0xa275c338…fc1a

0x34b655…2a6f

4 touches
1 conflict

0xb9b4eff6…c3ef

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdf64e5e6…75e8

0x34b655…2a6f

4 touches
1 conflict

0xfcc8f826…7c5f

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