← previous blocknext block →recent activity

Analyzing

Block #100,750,839

21 transactions · 19 stateful · 2026-08-31 12:02:27 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,750,839  ·  21 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

0x002fed35…79fa

0x2a68ba…90c5

14 touches
21 conflicts

0x103a6daa…7e9b

0x851145…3f07

13 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

6 touches
3 conflicts

0xf52df78b…16a0

0x851145…3f07

4 touches
1 conflict

0x07b86c51…cdae

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 0x002fed350f…7379fa

← previous block·next block →recent activity