← previous blocknext block →recent activity

Analyzing

Block #102,694,742

19 transactions · 17 stateful · 2026-09-07 07:30:21 UTC

Parallelism

89/100

Blocked

12%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #102,694,742  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd66696e0…0842

0x34b655…2a6f

4 touches
1 conflict

0xfaf5fe80…1ffc

0x34b655…2a6f

4 touches
1 conflict

0x359866c7…de7b

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x39fc983b…2a6f

0x34b655…2a6f

3 touches
1 conflict

0x9c1e9fb5…b7a6

0x34b655…2a6f

2 touches
0 conflicts

0xa9a9d0e0…4087

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0xd66696e0dc…230842

← previous block·next block →recent activity