← previous blocknext block →recent activity

Analyzing

Block #102,219,334

23 transactions · 22 stateful · 2026-09-05 15:23:35 UTC

Parallelism

78/100

Blocked

32%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,219,334  ·  23 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xc4c059d8…185d

0x34b655…2a6f

6 touches
3 conflicts

0x56a284d9…32e4

0x34b655…2a6f

4 touches
1 conflict

0x581b829b…9578

0x34b655…2a6f

4 touches
1 conflict

0x5ad364dd…07df

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…aaff

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…ab00

0x34b655…2a6f

4 touches
1 conflict

0x5eb187dd…b1d6

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 0xc824469a90…af6425

← previous block·next block →recent activity