← previous blocknext block →recent activity

Analyzing

Block #102,844,238

26 transactions · 25 stateful · 2026-09-07 20:05:45 UTC

Parallelism

69/100

Blocked

48%

Avg conflicts / tx

1.12

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,844,238  ·  26 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

0x9c168b41…7486

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x5c006808…f410

0x34b655…2a6f

8 touches
6 conflicts

0x74e46435…fdcd

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x0a3bbea4…529a

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

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 0x9c168b41b3…567486

← previous block·next block →recent activity