← previous blocknext block →recent activity

Analyzing

Block #101,065,672

21 transactions · 19 stateful · 2026-09-01 14:26:44 UTC

Parallelism

67/100

Blocked

58%

Avg conflicts / tx

1.24

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #101,065,672  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xaad6be10…0801

0x2a68ba…90c5

8 touches
6 conflicts

0x41c56387…a8f6

0x34b655…2a6f

6 touches
3 conflicts

0xf95f86cd…e927

0x34b655…2a6f

4 touches
1 conflict

0x5ba17602…af4f

0x34b655…2a6f

4 touches
1 conflict

0x70e677f5…e3bd

0x34b655…2a6f

4 touches
1 conflict

0x845ec8b0…c1af

0x34b655…2a6f

4 touches
1 conflict

0xa8ec03e3…eb22

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity