← previous blocknext block →recent activity

Analyzing

Block #101,094,202

22 transactions · 19 stateful · 2026-09-01 16:50:32 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,094,202  ·  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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x38bcfe5f…6c71

0x34b655…2a6f

4 touches
1 conflict

0x7b55ed0a…aed9

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd1b40f29…9b9d

0x34b655…2a6f

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

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: Market-MON/USDC

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity