← previous blocknext block →recent activity

Analyzing

Block #102,640,629

25 transactions · 21 stateful · 2026-09-07 02:58:07 UTC

Parallelism

76/100

Blocked

43%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,640,629  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xbb8dd99f…bb3f

0x851145…3f07

4 touches
1 conflict

0x989a0f70…96bf

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x413476a1…3e03

0x851145…3f07

4 touches
1 conflict

0xb1a4d6b6…304f

0x01bff4…1071

2 touches
0 conflicts

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity