← previous blocknext block →recent activity

Analyzing

Block #104,196,844

21 transactions · 20 stateful · 2026-09-12 13:55:25 UTC

Parallelism

76/100

Blocked

35%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #104,196,844  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x52e69143…95ad

0x065c9d…c394

8 touches
6 conflicts

0xce827910…ff22

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xd1512ecb…b583

0x065c9d…c394

5 touches
3 conflicts

0xd4b5b208…801d

0x065c9d…c394

5 touches
3 conflicts

0x7fe42a72…d24c

0x065c9d…c394

5 touches
3 conflicts

0x6c6f37ba…c20b

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

6 conflicts on slot 0x52e6914362…6e95ad

← previous block·next block →recent activity