← previous blocknext block →recent activity

Analyzing

Block #102,042,751

21 transactions · 19 stateful · 2026-09-05 00:28:28 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,042,751  ·  21 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

0x5746581b…0cb1

0x34b655…2a6f

6 touches
3 conflicts

0x67043b0b…97d7

0x34b655…2a6f

6 touches
3 conflicts

0x67c1f465…38b3

0x34b655…2a6f

6 touches
3 conflicts

0x04d4f30d…4dfb

0x34b655…2a6f

6 touches
3 conflicts

0x898a08aa…c855

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xcc8b6d32…6601

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 0x5746581b22…f30cb1

← previous block·next block →recent activity