← previous blocknext block →recent activity

Analyzing

Block #102,058,450

20 transactions · 19 stateful · 2026-09-05 01:48:00 UTC

Parallelism

85/100

Blocked

37%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,058,450  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x811723dc…307e

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x5e3014f0…b4e1

0x34b655…2a6f

4 touches
1 conflict

0x6a9e408e…3721

0x34b655…2a6f

4 touches
1 conflict

0x7daf6443…fd36

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

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 0xd66696e0dc…230842

← previous block·next block →recent activity