← previous blocknext block →recent activity

Analyzing

Block #102,248,313

26 transactions · 24 stateful · 2026-09-05 17:50:28 UTC

Parallelism

65/100

Blocked

38%

Avg conflicts / tx

1.5

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #102,248,313  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x51fc8795…126f

0x34b655…2a6f

18 touches
36 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

16 touches
28 conflicts

0x7dd96c96…7335

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x045532dd…4b7d

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

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 0x51fc8795c8…57126f

← previous block·next block →recent activity