← previous blocknext block →recent activity

Analyzing

Block #101,311,516

20 transactions · 15 stateful · 2026-09-02 11:03:49 UTC

Parallelism

80/100

Blocked

53%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,311,516  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…0002

0xf5b5f7…6d70

8 touches
6 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x213ee207…a151

0x34ae4d…3fc5

4 touches
1 conflict

0x46279ae7…20dd

0x34ae4d…3fc5

4 touches
1 conflict

0x53e50026…6d8c

0x34ae4d…3fc5

4 touches
1 conflict

0x6eff310a…c34c

0x34ae4d…3fc5

4 touches
1 conflict

0x7f4a8466…f2cc

0x34ae4d…3fc5

4 touches
1 conflict

0xe49b1b9b…0be1

0x34ae4d…3fc5

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: 0xf5b5f7f8…a36d70

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity