← previous blocknext block →recent activity

Analyzing

Block #102,116,723

23 transactions · 22 stateful · 2026-09-05 06:43:37 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,116,723  ·  23 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

0x8766f909…3683

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6a9e408e…3721

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x839c0c71…bada

0x34b655…2a6f

4 touches
1 conflict

0x90a021f0…f922

0x34b655…2a6f

4 touches
1 conflict

0xa4e9800f…4ab1

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 0x8766f90938…5f3683

← previous block·next block →recent activity