← previous blocknext block →recent activity

Analyzing

Block #102,266,968

23 transactions · 23 stateful · 2026-09-05 19:25:00 UTC

Parallelism

65/100

Blocked

35%

Avg conflicts / tx

0.83

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,266,968  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0x53c41998…7d52

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x0dbb4745…3b18

0x34b655…2a6f

8 touches
6 conflicts

0x706c758c…2fdb

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0xa169711f…c7f3

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity