← previous blocknext block →recent activity

Analyzing

Block #102,564,349

20 transactions · 18 stateful · 2026-09-06 20:32:08 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,564,349  ·  20 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

0x53c41998…7d52

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x43a82efb…51c8

0x34b655…2a6f

5 touches
3 conflicts

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0xc25a0525…63c8

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 0x53c41998b8…357d52

← previous block·next block →recent activity