← previous blocknext block →recent activity

Analyzing

Block #100,605,696

23 transactions · 20 stateful · 2026-08-30 23:52:21 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,605,696  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x7f5a78ab…e376

0x065c9d…c394

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x11258774…9892

0x2a68ba…90c5

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x36918c55…8424

0x34b655…2a6f

4 touches
1 conflict

0x451e482b…7e7d

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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

6 conflicts on slot 0x7f5a78abe4…b8e376

← previous block·next block →recent activity