← previous blocknext block →recent activity

Analyzing

Block #102,745,106

22 transactions · 18 stateful · 2026-09-07 11:43:45 UTC

Parallelism

86/100

Blocked

39%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,745,106  ·  22 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

0x0778475b…bd75

0x2a68ba…90c5

6 touches
3 conflicts

0x0661272f…6b2b

0x065c9d…c394

6 touches
3 conflicts

0x947bb79d…6458

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd66696e0…0842

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfaf5fe80…1ffc

0x34b655…2a6f

4 touches
1 conflict

0xfee9c1d5…61d6

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

3 conflicts on slot 0x0778475bb2…63bd75

← previous block·next block →recent activity