← previous blocknext block →recent activity

Analyzing

Block #102,855,749

24 transactions · 14 stateful · 2026-09-07 21:03:39 UTC

Parallelism

75/100

Blocked

57%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,855,749  ·  24 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

0x107b17c3…f6aa

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x1e602875…e2a7

0x34b655…2a6f

8 touches
6 conflicts

0xb6ed511f…6b68

0x34b655…2a6f

6 touches
3 conflicts

0x4188cc5f…2d2e

0x34b655…2a6f

6 touches
3 conflicts

0x470b41f6…fc68

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004b

0x80c745…7210

6 touches
3 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

10 conflicts on slot 0x107b17c354…59f6aa

← previous block·next block →recent activity