← previous blocknext block →recent activity

Analyzing

Block #104,198,623

10 transactions · 10 stateful · 2026-09-12 14:04:27 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #104,198,623  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x1a2055c7…9054

0x34b655…2a6f

4 touches
1 conflict

0x640c4fb2…044a

0x34b655…2a6f

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0xbceecf11…0120

0x34b655…2a6f

4 touches
1 conflict

0xc7cf05d4…7fa5

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641d

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

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

1 conflict on slot 0xce827910a4…82ff22

← previous block·next block →recent activity