← previous blocknext block →recent activity

Analyzing

Block #100,740,930

20 transactions · 18 stateful · 2026-08-31 11:12:36 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,740,930  ·  20 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

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x41c56387…a8f6

0x34b655…2a6f

4 touches
1 conflict

0x535293b7…e570

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0xa507cf9e…44a9

0x34b655…2a6f

4 touches
1 conflict

0xb9ab93a0…f656

0x34b655…2a6f

4 touches
1 conflict

0xfa09be5a…1e79

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 0x0000000000…00003d

← previous block·next block →recent activity