← previous blocknext block →recent activity

Analyzing

Block #102,394,692

19 transactions · 16 stateful · 2026-09-06 06:12:06 UTC

Parallelism

63/100

Blocked

56%

Avg conflicts / tx

1.26

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,394,692  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

12 touches
15 conflicts

0xb5cddf91…0abf

0x34b655…2a6f

10 touches
10 conflicts

0x7aad02c6…b979

0x34b655…2a6f

10 touches
10 conflicts

0xd6a0a7b8…fb34

0x34b655…2a6f

6 touches
3 conflicts

0xba0fd3cf…a6cc

0x34b655…2a6f

6 touches
3 conflicts

0xdc7b9eda…e616

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

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