← previous blocknext block →recent activity

Analyzing

Block #102,096,772

25 transactions · 19 stateful · 2026-09-05 05:02:25 UTC

Parallelism

84/100

Blocked

37%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,096,772  ·  25 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

0x68531239…e9a3

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x101be604…5db0

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x729d8210…e2aa

0x34b655…2a6f

4 touches
1 conflict

0x89ac61bf…9443

0x34b655…2a6f

4 touches
1 conflict

0x9327d918…2a0a

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

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

6 conflicts on slot 0x68531239f9…5ae9a3

← previous block·next block →recent activity