← previous blocknext block →recent activity

Analyzing

Block #101,322,827

21 transactions · 16 stateful · 2026-09-02 12:00:43 UTC

Parallelism

86/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,322,827  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb686e6f5…f6d1

0xc8689a…ee79

4 touches
1 conflict

0x2528e717…2a22

0x34b655…2a6f

4 touches
1 conflict

0x676b5eb4…0b33

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbb975a6c…bff4

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xa4ca6ac1…d1c8

0xa6afd3…d132

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: Perpl: Settlement / Helper

1 conflict on slot 0xb686e6f57a…53f6d1

← previous block·next block →recent activity