← previous blocknext block →recent activity

Analyzing

Block #102,249,991

24 transactions · 21 stateful · 2026-09-05 17:58:57 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,249,991  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0xc21a95c7…9a0d

0x34b655…2a6f

8 touches
6 conflicts

0xc1da8f73…484c

0x34b655…2a6f

8 touches
6 conflicts

0x14be574b…a3e7

0x34b655…2a6f

7 touches
6 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

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 0x482471adbb…39122f

← previous block·next block →recent activity