← previous blocknext block →recent activity

Analyzing

Block #100,855,484

27 transactions · 24 stateful · 2026-08-31 20:49:17 UTC

Parallelism

56/100

Blocked

75%

Avg conflicts / tx

1.85

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #100,855,484  ·  27 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

14 touches
21 conflicts

0x892daf6e…48d8

0x065c9d…c394

14 touches
21 conflicts

0xb686e6f5…f6d1

0xc8689a…ee79

12 touches
15 conflicts

0xa605468c…1bfc

0x34ae4d…3fc5

12 touches
15 conflicts

0x06e40499…165e

0x34ae4d…3fc5

12 touches
15 conflicts

0xe9976b4c…ee7e

0x065c9d…c394

12 touches
15 conflicts

0xaad6be10…0801

0x2a68ba…90c5

12 touches
15 conflicts

0xb3d07e16…37f0

0xd32edf…ff58

11 touches
15 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 0x0000000000…00003d

← previous block·next block →recent activity