← previous blocknext block →recent activity

Analyzing

Block #102,279,154

25 transactions · 23 stateful · 2026-09-05 20:26:49 UTC

Parallelism

72/100

Blocked

35%

Avg conflicts / tx

1.24

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,279,154  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xb1292e82…28ab

0x34b655…2a6f

8 touches
6 conflicts

0x22f10271…841d

0x34b655…2a6f

8 touches
6 conflicts

0x706c758c…2fdb

0x34b655…2a6f

6 touches
3 conflicts

0x820d7282…6c34

0x34b655…2a6f

6 touches
3 conflicts

0x839c0c71…bada

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

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

21 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity