← previous blocknext block →recent activity

Analyzing

Block #102,307,954

22 transactions · 19 stateful · 2026-09-05 22:52:40 UTC

Parallelism

64/100

Blocked

42%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,307,954  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x7dd96c96…7335

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2d75a923…c236

0x34b655…2a6f

4 touches
1 conflict

0x4fb22186…c457

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x820d7282…6c34

0x34b655…2a6f

4 touches
1 conflict

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity