← previous blocknext block →recent activity

Analyzing

Block #102,875,564

20 transactions · 18 stateful · 2026-09-07 22:43:21 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x55010ec8…ea31

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x9862de7d…8c73

0x34b655…2a6f

4 touches
1 conflict

0xa68eac07…7041

0x34b655…2a6f

4 touches
1 conflict

0xba71b2e5…5652

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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

← previous block·next block →recent activity