← previous blocknext block →recent activity

Analyzing

Block #102,868,119

21 transactions · 20 stateful · 2026-09-07 22:05:53 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.52

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,868,119  ·  21 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

0x5c0f61f5…6909

0x34b655…2a6f

6 touches
3 conflicts

0x83f284e0…d141

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x0dd3d3cd…7281

0x34b655…2a6f

4 touches
1 conflict

0x2e1f5171…ad2d

0x34b655…2a6f

4 touches
1 conflict

0x35a36a09…b479

0x34b655…2a6f

4 touches
1 conflict

0x46e2bb67…d8b3

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 0x5c0f61f54d…606909

← previous block·next block →recent activity