← previous blocknext block →recent activity

Analyzing

Block #102,138,689

22 transactions · 18 stateful · 2026-09-05 08:34:54 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,138,689  ·  22 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

0x91b13e91…855d

0x34b655…2a6f

14 touches
21 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x38de0bc5…b875

0x34b655…2a6f

10 touches
10 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
3 conflicts

0x922cbc0c…51aa

0x34b655…2a6f

6 touches
3 conflicts

0xd0f91ee4…9a53

0x34b655…2a6f

5 touches
3 conflicts

0xdc7b9eda…e616

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 0x91b13e914b…cb855d

← previous block·next block →recent activity