← previous blocknext block →recent activity

Analyzing

Block #101,092,235

16 transactions · 15 stateful · 2026-09-01 16:40:38 UTC

Parallelism

69/100

Blocked

53%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,092,235  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0x3e1e8e54…9c83

0x2a68ba…90c5

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x46279ae7…20dd

0x34ae4d…3fc5

4 touches
1 conflict

0x6eff310a…c34c

0x34ae4d…3fc5

4 touches
1 conflict

0xb55a7cbc…68f5

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: Perpl

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity