← previous blocknext block →recent activity

Analyzing

Block #100,093,365

38 transactions · 24 stateful · 2026-08-29 04:50:23 UTC

Parallelism

82/100

Blocked

63%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,093,365  ·  38 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x348fda08…7e96

0x065c9d…c394

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0x06e40499…165e

0x2b46c0…1669

12 touches
15 conflicts

0xa605468c…1bfc

0x2b46c0…1669

12 touches
15 conflicts

0xbb97db90…4c93

0xc8689a…ee79

12 touches
15 conflicts

0x11258774…9892

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…0002

0xf5b5f7…6d70

10 touches
10 conflicts

0xf2ec911c…93ee

0xd32edf…ff58

9 touches
10 conflicts

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

21 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity