← previous blocknext block →recent activity

Analyzing

Block #101,672,989

25 transactions · 22 stateful · 2026-09-03 17:22:30 UTC

Parallelism

76/100

Blocked

36%

Avg conflicts / tx

0.4

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,672,989  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x51af0e92…4020

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xdbb571e4…6829

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x1a2e73cf…5ff5

0x34b655…2a6f

2 touches
0 conflicts

0x2222135b…8843

0x34b655…2a6f

2 touches
0 conflicts

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 0xb3fb9fb561…7664db

← previous block·next block →recent activity