← previous blocknext block →recent activity

Analyzing

Block #102,379,082

19 transactions · 19 stateful · 2026-09-06 04:53:00 UTC

Parallelism

79/100

Blocked

37%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,379,082  ·  19 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbbc4bdf7…c62f

0x34b655…2a6f

6 touches
3 conflicts

0x08cc68a2…2a59

0x34b655…2a6f

4 touches
1 conflict

0x14f03197…2dba

0x34b655…2a6f

4 touches
1 conflict

0x3f775186…af22

0x34b655…2a6f

4 touches
1 conflict

0x4d5053d1…3b7d

0x34b655…2a6f

4 touches
1 conflict

0x502b3ee1…7f7c

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 0x482471adbb…39122f

← previous block·next block →recent activity