← previous blocknext block →recent activity

Analyzing

Block #102,670,818

16 transactions · 14 stateful · 2026-09-07 05:29:59 UTC

Parallelism

63/100

Blocked

57%

Avg conflicts / tx

1.25

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,670,818  ·  16 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

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0x2c539d94…b63a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641d

0x34b655…2a6f

6 touches
3 conflicts

0x0d2d23d3…8a3a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…642d

0x34b655…2a6f

6 touches
3 conflicts

0x9cf9008a…d826

0x34b655…2a6f

5 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

15 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity