← previous blocknext block →recent activity

Analyzing

Block #102,231,228

22 transactions · 21 stateful · 2026-09-05 16:23:49 UTC

Parallelism

55/100

Blocked

67%

Avg conflicts / tx

2

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #102,231,228  ·  22 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xc824469a…6425

0x34b655…2a6f

18 touches
36 conflicts

0x482471ad…122f

0x34b655…2a6f

16 touches
28 conflicts

0xe4d331fb…33f3

0x34b655…2a6f

14 touches
21 conflicts

0x29a58269…011a

0x34b655…2a6f

6 touches
3 conflicts

0x60a536a6…ef7a

0x34b655…2a6f

6 touches
3 conflicts

0x6c7c1a4b…5751

0x34b655…2a6f

6 touches
3 conflicts

0x7c216fca…20cb

0x34b655…2a6f

6 touches
3 conflicts

0x7daf6443…fd36

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

36 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity