← previous blocknext block →recent activity

Analyzing

Block #102,695,013

20 transactions · 18 stateful · 2026-09-07 07:31:43 UTC

Parallelism

85/100

Blocked

39%

Avg conflicts / tx

0.55

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,695,013  ·  20 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

0xbd22d0fc…64fd

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6d8ad688…4bf5

0xa6afd3…d132

4 touches
1 conflict

0x3319b5a6…e83a

0x34b655…2a6f

4 touches
1 conflict

0x38ffda89…25b9

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0xbd22d0fc04…0464fd

← previous block·next block →recent activity