← previous blocknext block →recent activity

Analyzing

Block #102,251,049

23 transactions · 21 stateful · 2026-09-05 18:04:18 UTC

Parallelism

65/100

Blocked

38%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,251,049  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0xd842b906…a093

0x34b655…2a6f

6 touches
3 conflicts

0x5e0b8bbe…377b

0x34b655…2a6f

4 touches
1 conflict

0x5eb187dd…b1d6

0x34b655…2a6f

4 touches
1 conflict

0x6bab0076…422b

0x34b655…2a6f

4 touches
1 conflict

0x6f6fc26c…3e34

0x34b655…2a6f

4 touches
1 conflict

0x7c2869d6…1203

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity