← previous blocknext block →recent activity

Analyzing

Block #101,842,301

22 transactions · 20 stateful · 2026-09-04 07:34:06 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,842,301  ·  22 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

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x736b9166…5ea5

0x34b655…2a6f

6 touches
3 conflicts

0x20b1228b…2487

0x34b655…2a6f

4 touches
1 conflict

0x6324ccc9…14fd

0x34b655…2a6f

4 touches
1 conflict

0x6ca15e14…7be8

0x34b655…2a6f

4 touches
1 conflict

0xe181f491…f4e3

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

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 0xbde524f475…b143bf

← previous block·next block →recent activity