← previous blocknext block →recent activity

Analyzing

Block #102,009,509

22 transactions · 20 stateful · 2026-09-04 21:40:11 UTC

Parallelism

64/100

Blocked

45%

Avg conflicts / tx

0.91

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,009,509  ·  22 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

12 touches
15 conflicts

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0x7dd96c96…7335

0x34b655…2a6f

8 touches
6 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x6974210b…154c

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x02803960…b9c0

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