← previous blocknext block →recent activity

Analyzing

Block #101,094,921

22 transactions · 19 stateful · 2026-09-01 16:54:09 UTC

Parallelism

64/100

Blocked

47%

Avg conflicts / tx

1.09

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #101,094,921  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0x1f0c043e…3dba

0xd32edf…ff58

9 touches
10 conflicts

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb87af72a…aef6

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

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

10 conflicts on slot 0xaad6be10ae…2c0801

← previous block·next block →recent activity