← previous blocknext block →recent activity

Analyzing

Block #102,654,045

18 transactions · 18 stateful · 2026-09-07 04:05:36 UTC

Parallelism

72/100

Blocked

33%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,654,045  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x1513b999…b52e

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x7c216fca…20cb

0x34b655…2a6f

6 touches
3 conflicts

0x7fd951f1…fe49

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x999c658d…b185

0x34b655…2a6f

6 touches
3 conflicts

0xb826ef15…d248

0x34b655…2a6f

6 touches
3 conflicts

0xda50c9d5…674e

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

3 conflicts on slot 0x1513b999be…b2b52e

← previous block·next block →recent activity