← previous blocknext block →recent activity

Analyzing

Block #102,483,800

27 transactions · 21 stateful · 2026-09-06 13:43:32 UTC

Parallelism

74/100

Blocked

43%

Avg conflicts / tx

0.56

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,483,800  ·  27 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

0xaad6be10…0801

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x6ccfb721…7802

0xd32edf…ff58

5 touches
3 conflicts

0x70d11b52…353f

0x065c9d…c394

5 touches
3 conflicts

0xd987be6c…47f1

0x754704…b603

4 touches
1 conflict

0xf91b744e…9117

0x754704…b603

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

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: MarginAccount

6 conflicts on slot 0xaad6be10ae…2c0801

← previous block·next block →recent activity