← previous blocknext block →recent activity

Analyzing

Block #102,349,405

20 transactions · 19 stateful · 2026-09-06 02:22:43 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,349,405  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf416c7e0…8b2c

0x34b655…2a6f

6 touches
3 conflicts

0x931975c2…b7b3

0x34b655…2a6f

6 touches
3 conflicts

0x1f396cee…862f

0x34b655…2a6f

4 touches
1 conflict

0xa4e9800f…4ab1

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x422d5490…52d9

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

3 conflicts on slot 0xf416c7e090…1d8b2c

← previous block·next block →recent activity