← previous blocknext block →recent activity

Analyzing

Block #102,048,629

17 transactions · 15 stateful · 2026-09-05 00:58:14 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,048,629  ·  17 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

0x29a58269…011a

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0xa1a01ded…c087

0x34b655…2a6f

6 touches
3 conflicts

0xa2c04336…e4c0

0x34b655…2a6f

6 touches
3 conflicts

0xb826ef15…d248

0x34b655…2a6f

6 touches
3 conflicts

0xbb9ab337…f4ec

0x34b655…2a6f

6 touches
3 conflicts

0x02372d42…1871

0x34b655…2a6f

6 touches
3 conflicts

0xddf10453…d774

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

3 conflicts on slot 0x29a582695b…cf011a

← previous block·next block →recent activity