← previous blocknext block →recent activity

Analyzing

Block #102,379,568

18 transactions · 17 stateful · 2026-09-06 04:55:27 UTC

Parallelism

56/100

Blocked

53%

Avg conflicts / tx

1.56

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,379,568  ·  18 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

14 touches
21 conflicts

0x1a5de8bb…7bc7

0x34b655…2a6f

6 touches
3 conflicts

0xbbc4bdf7…c62f

0x34b655…2a6f

6 touches
3 conflicts

0x045532dd…4b7d

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x99479bc5…3a88

0x34b655…2a6f

4 touches
1 conflict

0xa842b63d…fb2b

0x34b655…2a6f

4 touches
1 conflict

0xb75367ff…a2b7

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity