← previous blocknext block →recent activity

Analyzing

Block #102,552,233

15 transactions · 15 stateful · 2026-09-06 19:30:41 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

0.8

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,552,233  ·  15 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xb0e974c4…b84d

0x34b655…2a6f

4 touches
1 conflict

0xbceecf11…0120

0x34b655…2a6f

4 touches
1 conflict

0xbdfb6b06…2189

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0xf8d3825f…685d

0x34b655…2a6f

4 touches
1 conflict

0x42e5184f…4e8b

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity