← previous blocknext block →recent activity

Analyzing

Block #102,670,775

18 transactions · 18 stateful · 2026-09-07 05:29:46 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,670,775  ·  18 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

6 touches
3 conflicts

0xd78b946a…ecce

0x34b655…2a6f

4 touches
1 conflict

0xea3b49a7…24d7

0x34b655…2a6f

4 touches
1 conflict

0xf63c2a2b…bc5f

0x34b655…2a6f

4 touches
1 conflict

0xf63c2a2b…bc60

0x34b655…2a6f

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0xb575cf74…fbd5

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

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

← previous block·next block →recent activity