← previous blocknext block →recent activity

Analyzing

Block #102,055,276

18 transactions · 16 stateful · 2026-09-05 01:31:56 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,055,276  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf0e7ad63…ef51

0x34b655…2a6f

8 touches
6 conflicts

0xc0f6895c…e428

0x34b655…2a6f

6 touches
3 conflicts

0xc853be2d…b18f

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x9bff3222…a246

0x34b655…2a6f

6 touches
3 conflicts

0x9c088939…ddd7

0x34b655…2a6f

6 touches
3 conflicts

0x173b64af…6c43

0x34b655…2a6f

6 touches
3 conflicts

0x897879a1…9c78

0x34b655…2a6f

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

6 conflicts on slot 0xf0e7ad6377…3eef51

← previous block·next block →recent activity