← previous blocknext block →recent activity

Analyzing

Block #102,810,551

26 transactions · 24 stateful · 2026-09-07 17:16:08 UTC

Parallelism

73/100

Blocked

46%

Avg conflicts / tx

1.42

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,810,551  ·  26 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

0x6518075e…2b17

0x2a68ba…90c5

14 touches
21 conflicts

0x1472ea0c…6cd1

0x40c49f…2af0

13 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0xd17580f9…ece1

0x754704…b603

8 touches
6 conflicts

0x2b54cadb…4425

0xd18b7e…414b

8 touches
6 conflicts

0x24476107…ba32

0x065c9d…c394

4 touches
1 conflict

0x3e1e8e54…9c83

0x2a68ba…90c5

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

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

21 conflicts on slot 0x6518075e89…5f2b17

← previous block·next block →recent activity