← previous blocknext block →recent activity

Analyzing

Block #102,706,139

25 transactions · 24 stateful · 2026-09-07 08:27:42 UTC

Parallelism

76/100

Blocked

29%

Avg conflicts / tx

0.6

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,706,139  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x9f313616…3aed

0x065c9d…c394

10 touches
10 conflicts

0x0778475b…bd75

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xb87af72a…aef6

0x2a68ba…90c5

4 touches
1 conflict

0x48ed1159…abe9

0x34ae4d…3fc5

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0xa9a9d0e0…4087

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

10 conflicts on slot 0x9f31361649…b53aed

← previous block·next block →recent activity