← previous blocknext block →recent activity

Analyzing

Block #102,378,780

25 transactions · 21 stateful · 2026-09-06 04:51:27 UTC

Parallelism

60/100

Blocked

48%

Avg conflicts / tx

1.04

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #102,378,780  ·  25 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x14f03197…2dba

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x64d501ff…42cf

0x34b655…2a6f

4 touches
1 conflict

0xa418f585…39b0

0x34b655…2a6f

4 touches
1 conflict

0xaf92416c…1d14

0x34b655…2a6f

4 touches
1 conflict

0xc4feec13…d1b9

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 0xca841faae5…71486a

← previous block·next block →recent activity