← previous blocknext block →recent activity

Analyzing

Block #102,205,458

19 transactions · 19 stateful · 2026-09-05 14:13:24 UTC

Parallelism

74/100

Blocked

37%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,205,458  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x1a2055c7…9054

0x34b655…2a6f

4 touches
1 conflict

0x3f775186…af22

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0xfdcb3208…9be0

0x34b655…2a6f

4 touches
1 conflict

0x09e0690d…6e3d

0xe52b14…7230

4 touches
1 conflict

0x17bbe4f8…08c5

0xe52b14…7230

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity