← previous blocknext block →recent activity

Analyzing

Block #102,060,858

21 transactions · 18 stateful · 2026-09-05 02:00:13 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,060,858  ·  21 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

8 touches
6 conflicts

0x71b395d9…1697

0x34b655…2a6f

8 touches
6 conflicts

0x8cecfed5…f339

0x34b655…2a6f

8 touches
6 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
3 conflicts

0x109d8a52…a7b7

0x34b655…2a6f

6 touches
3 conflicts

0x5a14427b…8dc5

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