← previous blocknext block →recent activity

Analyzing

Block #102,655,236

20 transactions · 19 stateful · 2026-09-07 04:11:36 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,655,236  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0xf7772b49…fc12

0x34b655…2a6f

6 touches
3 conflicts

0x01315072…0e2d

0x34b655…2a6f

6 touches
3 conflicts

0x3a02129f…9eaf

0x34b655…2a6f

6 touches
3 conflicts

0x448fdf2a…fab4

0x34b655…2a6f

6 touches
3 conflicts

0x67043b0b…97d7

0x34b655…2a6f

6 touches
3 conflicts

0x6823c28e…594c

0x34b655…2a6f

6 touches
3 conflicts

0x7e273bc0…5dbc

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 0x51fc8795c8…57126f

← previous block·next block →recent activity