← previous blocknext block →recent activity

Analyzing

Block #102,174,508

22 transactions · 19 stateful · 2026-09-05 11:36:32 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.82

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,174,508  ·  22 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

0xe5bb3628…e5f1

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xb5cddf91…0abf

0x34b655…2a6f

10 touches
10 conflicts

0x7aad02c6…b979

0x34b655…2a6f

10 touches
10 conflicts

0x9c92f16a…5db2

0x34b655…2a6f

6 touches
3 conflicts

0x6fc24f20…f3c7

0x34b655…2a6f

6 touches
3 conflicts

0x2eb15031…f48d

0x34b655…2a6f

6 touches
3 conflicts

0x74462c1e…84f3

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 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity