← previous blocknext block →recent activity

Analyzing

Block #108,496,464

35 transactions · 29 stateful · 2026-09-27 15:05:30 UTC

Parallelism

94/100

Blocked

14%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #108,496,464  ·  35 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

0x16d77246…bac5

0x34b655…2a6f

4 touches
1 conflict

0xbd3735d7…c973

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5e8

0x34b655…2a6f

4 touches
1 conflict

0xf4a97154…2d71

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

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