← previous blocknext block →recent activity

Analyzing

Block #102,206,117

22 transactions · 18 stateful · 2026-09-05 14:16:44 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,206,117  ·  22 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

6 touches
3 conflicts

0x113a6203…5dd8

0x34b655…2a6f

6 touches
3 conflicts

0x9a8af3c2…e4ae

0x34b655…2a6f

6 touches
3 conflicts

0xcc8faac2…c766

0x065c9d…c394

4 touches
1 conflict

0x5b0621ee…3c2c

0x284f45…7777

4 touches
1 conflict

0xa164d951…1534

0xe1c8b7…3022

4 touches
1 conflict

0x41c56387…a8f6

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity