← previous blocknext block →recent activity

Analyzing

Block #102,744,822

13 transactions · 12 stateful · 2026-09-07 11:42:20 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,744,822  ·  13 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0xef048f92…572b

0x34b655…2a6f

4 touches
1 conflict

0xfaf5fe80…1ffc

0x34b655…2a6f

4 touches
1 conflict

0x2ebc47f3…2d5c

0x34b655…2a6f

4 touches
1 conflict

0x4f089e20…f71a

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 0xc824469a90…af6425

← previous block·next block →recent activity