← previous blocknext block →recent activity

Analyzing

Block #102,287,193

25 transactions · 22 stateful · 2026-09-05 21:07:35 UTC

Parallelism

80/100

Blocked

32%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,287,193  ·  25 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

0xa0a435fa…8773

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xa4e9800f…4ab1

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0x6636a104…d595

0x34b655…2a6f

6 touches
3 conflicts

0x9cf9008a…d826

0x34b655…2a6f

6 touches
3 conflicts

0x990bf0c1…a307

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

10 conflicts on slot 0xa0a435fad2…0b8773

← previous block·next block →recent activity