← previous blocknext block →recent activity

Analyzing

Block #100,456,334

11 transactions · 11 stateful · 2026-08-30 11:20:58 UTC

Parallelism

82/100

Blocked

27%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,456,334  ·  11 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x141dcc2b…e8d9

0x34b655…2a6f

4 touches
1 conflict

0x152ab4b2…7fee

0x34b655…2a6f

4 touches
1 conflict

0x266a6b2c…4376

0x34b655…2a6f

4 touches
1 conflict

0x266a6b2c…4377

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xd476e5b1…12d1

0x34b655…2a6f

4 touches
1 conflict

0xf18fa6c1…4bf8

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