← previous blocknext block →recent activity

Analyzing

Block #102,544,364

18 transactions · 16 stateful · 2026-09-06 18:50:50 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,544,364  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb8f43c8d…77b2

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xcd31008f…f7b7

0x34b655…2a6f

4 touches
1 conflict

0x272e6316…bbe8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity